Triple
T4894349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smith Barney |
E109637
|
entity |
| Predicate | roleInCitigroup |
P43130
|
FINISHED |
| Object | core retail brokerage 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: core retail brokerage platform | Statement: [Smith Barney, roleInCitigroup, core retail brokerage platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCitigroup Context triple: [Smith Barney, roleInCitigroup, core retail brokerage platform]
-
A.
roleInIndustry
Indicates the specific function, position, or capacity an entity holds within a particular industry or sector.
-
B.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
-
C.
underlyingCompanyRole
chosen
Indicates the specific function, position, or responsibility an entity holds within or in relation to a company.
-
D.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
E.
roleInBankingHistory
Indicates that an entity has a specific function, contribution, or significance within the historical development of banking.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.