Triple
T8087344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Golden |
E188765
|
entity |
| Predicate | roleAtMiami |
P8234
|
FINISHED |
| Object | head football coach |
—
|
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: head football coach | Statement: [Al Golden, roleAtMiami, head football coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtMiami Context triple: [Al Golden, roleAtMiami, head football coach]
-
A.
roleAtMidway
Indicates that an entity holds or held a specific role, position, or function at the midpoint or intermediate stage of a process, event, or time period.
-
B.
roleInLasVegas
Indicates that an entity holds or held a specific role, position, or function within the context of Las Vegas (such as in its government, organizations, events, or productions).
-
C.
hasCityRole
chosen
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
D.
roleAtMemphis
Indicates that an entity holds or held a specific role or position at the organization or institution named Memphis.
-
E.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4162244481908ab1202a9974deaa |
completed | March 31, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69cb04a14cd88190a79ed26cbeec1c33 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:29 p.m.