Triple
T14117952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rodney McMullen |
E339821
|
entity |
| Predicate | executiveRoleType |
P5518
|
FINISHED |
| Object | public company 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: public company CEO | Statement: [Rodney McMullen, executiveRoleType, public company CEO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executiveRoleType Context triple: [Rodney McMullen, executiveRoleType, public company CEO]
-
A.
roleInExecutive
Indicates that an entity holds a specific position or function within an executive body or leadership structure.
-
B.
typeOfRole
chosen
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
executiveFor
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.
officeHolderRoleIn
Indicates that an entity holds or has held a specific role or position within a particular office or organizational context.
-
E.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de609322ac8190bb389ca250882af5 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.