Triple
T36095272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Executive Officer of Koch Industries |
E1044041
|
entity |
| Predicate | mayAlsoHoldRole |
P28456
|
FINISHED |
| Object | Chairman of Koch Industries |
—
|
NE NERFINISHED |
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: Chairman of Koch Industries | Statement: [Chief Executive Officer of Koch Industries, mayAlsoHoldRole, Chairman of Koch Industries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayAlsoHoldRole Context triple: [Chief Executive Officer of Koch Industries, mayAlsoHoldRole, Chairman of Koch Industries]
-
A.
mayHaveRole
Indicates that an entity is permitted or eligible to hold or perform a specified role.
-
B.
possibleRole
chosen
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
-
C.
mayHoldTitleOf
Indicates that an entity is permitted or eligible to possess or bear a particular title.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
mayHavePriorRole
Indicates that an entity is allowed or expected to have held a specified role at some earlier 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_69f76e32d60c8190ba781ffaaab4aa3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.