Triple
T24290432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1985 Minnesota Vikings season |
E605800
|
entity |
| Predicate | headCoachReturnFromRetirement |
P72267
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1985 Minnesota Vikings season, headCoachReturnFromRetirement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headCoachReturnFromRetirement Context triple: [1985 Minnesota Vikings season, headCoachReturnFromRetirement, true]
-
A.
headCoachEnd
Indicates the point in time or event at which an entity’s role or tenure as a head coach comes to an end.
-
B.
headCoachFrom
Indicates that one entity serves as the head coach and originates from, or is affiliated with, the location or organization represented by the other entity.
-
C.
returnedAsHeadCoach
chosen
Indicates that an individual resumed a previous role as head coach of a team or organization after a period of absence.
-
D.
headCoachTo
Indicates that one entity serves as the head coach of another entity, such as a team or organization.
-
E.
previousHeadCoach
Indicates that one entity formerly served as the head coach of the other entity before being replaced.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f29155e3cc8190808723d6b56dcfc0 |
completed | April 29, 2026, 11:16 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.