Triple
T13833948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rooney family |
E332475
|
entity |
| Predicate | notableMemberOccupation |
P47271
|
FINISHED |
| Object | NFL executive |
—
|
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: NFL executive | Statement: [Rooney family, notableMemberOccupation, NFL executive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberOccupation Context triple: [Rooney family, notableMemberOccupation, NFL executive]
-
A.
notableOccupationContext
Indicates that the referenced occupation is notable or significant specifically within the given contextual framework or domain.
-
B.
notableHolderOccupation
chosen
Indicates that a person notably associated with an entity (e.g., an award, office, or title) held a particular occupation or professional role.
-
C.
notableCharacterOccupation
Indicates that a notable character is associated with a specific occupation or professional role.
-
D.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
E.
employerOfNotablePerson
Indicates that an entity serves or has served as the employer of a person who is considered notable.
- 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_69d81c5ae7c88190b0dd41bdafeb5999 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de029a34bc8190ae892ef7b09fc9e9 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc86668e08190ba9135d1c3f38d35 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:13 p.m.