Triple
T3543746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TD Ameritrade |
E74945
|
entity |
| Predicate | offersAccountType |
P5098
|
FINISHED |
| Object | individual brokerage account |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: individual brokerage account | Statement: [TD Ameritrade, offersAccountType, individual brokerage account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersAccountType Context triple: [TD Ameritrade, offersAccountType, individual brokerage account]
-
A.
accountType
Indicates the specific category or classification of an account within a system or context.
-
B.
offersPlanType
Indicates that one entity provides or makes available a specific type of plan to another entity or in a given context.
-
C.
supportsAccountType
chosen
Indicates that one entity is compatible with, or able to operate for, a specified type or category of account.
-
D.
offersServiceType
Indicates that one entity provides or makes available a specific type or category of service to another entity or the public.
-
E.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ad85d274cc8190ab59c97298a1cfbf |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbf752dd481909226044ffe595338 |
completed | March 8, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.