Triple
T8087343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Golden |
E188765
|
entity |
| Predicate | roleAtTemple |
P80423
|
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, roleAtTemple, head football coach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtTemple Context triple: [Al Golden, roleAtTemple, head football coach]
-
A.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
B.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
C.
associatedWithTempleTown
Indicates a relationship where an entity has a connection or linkage to a town that is characterized by or centered around a temple.
-
D.
participatingTempleGroup
Indicates that a temple is a member of, or takes part in the activities of, a specific temple group or organization.
-
E.
roleInRitual
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:29 p.m.