Triple
T4672245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJR Nabisco |
E103590
|
entity |
| Predicate | keyExecutiveRole |
P46272
|
FINISHED |
| Object | CEO |
—
|
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: CEO | Statement: [RJR Nabisco, keyExecutiveRole, CEO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyExecutiveRole Context triple: [RJR Nabisco, keyExecutiveRole, CEO]
-
A.
keyPerson
Indicates that a person plays a primary, central, or critically important role in relation to an organization, project, or entity.
-
B.
leadershipPosition
Indicates that one entity holds a role of authority, guidance, or decision-making responsibility over others within an organization, group, or context.
-
C.
executiveFor
chosen
Indicates that one entity serves in an executive role (such as CEO, president, or similar leadership position) for another entity, typically an organization or company.
-
D.
keyOffice
Indicates that a key is associated with, grants access to, or is assigned to a particular office.
-
E.
capitalRoleUntil
Indicates that an entity served in the role of capital of another entity up to (but not necessarily including) a specified end time.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.