Triple
T32644645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tribal Chief |
E834566
|
entity |
| Predicate | managerRoleFor |
P130028
|
FINISHED |
| Object | Paul Heyman as Special Counsel |
—
|
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: Paul Heyman as Special Counsel | Statement: [The Tribal Chief, managerRoleFor, Paul Heyman as Special Counsel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managerRoleFor Context triple: [The Tribal Chief, managerRoleFor, Paul Heyman as Special Counsel]
-
A.
managementRole
chosen
Indicates that one entity holds a managerial or supervisory role with authority and responsibility over another entity.
-
B.
managerType
Indicates the specific category or role classification of a manager within an organizational or system context.
-
C.
managerFrom
Indicates that one entity serves as a manager originating from, or associated with, a specified source such as an organization, location, or department.
-
D.
libraryRole
Indicates the specific function, responsibility, or position an entity holds within the context of a library.
-
E.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of another entity.
- 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_69f3492e773c81908afc10651e46cad3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:07 a.m.