Triple
T27636219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottrade |
E696473
|
entity |
| Predicate | integrationAfterAcquisition |
P121366
|
FINISHED |
| Object | TD Ameritrade platform |
—
|
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: TD Ameritrade platform | Statement: [Scottrade, integrationAfterAcquisition, TD Ameritrade platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationAfterAcquisition Context triple: [Scottrade, integrationAfterAcquisition, TD Ameritrade platform]
-
A.
integrationOutcome
Indicates the result or consequence produced when two or more components, systems, or processes are combined or integrated.
-
B.
afterAcquisitionBy
chosen
Indicates that something occurs or holds true following the acquisition of one entity by another.
-
C.
ownershipAfterIntegration
Indicates that one entity holds ownership or control of another entity after a merger, acquisition, or integration process has been completed.
-
D.
acquisitionResultedIn
Indicates that an acquisition event led to a particular outcome, state, or consequence for the involved entities.
-
E.
previouslyIntegratedInto
Indicates that an entity was formerly incorporated or included as part of another entity or system in the past.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 2:24 p.m.