Triple
T4628044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Todd Bowles |
E101146
|
entity |
| Predicate | servedAsInterimHeadCoachYear |
P57528
|
FINISHED |
| Object | 2011 (Miami Dolphins) |
—
|
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: 2011 (Miami Dolphins) | Statement: [Todd Bowles, servedAsInterimHeadCoachYear, 2011 (Miami Dolphins)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsInterimHeadCoachYear Context triple: [Todd Bowles, servedAsInterimHeadCoachYear, 2011 (Miami Dolphins)]
-
A.
hiredAsHeadCoachYear
Indicates the year in which an individual was hired to serve as the head coach of a team or organization.
-
B.
headCoachTenure
Indicates the duration or period during which a specific individual serves as the head coach of a team or organization.
-
C.
signedAsHeadCoachBy
Indicates that an individual is formally appointed and contracted to serve in the role of head coach by a team or organization.
-
D.
replacedAsHeadCoach
Indicates that one person assumed the role of head coach in place of another, effectively succeeding them in that position.
-
E.
headCoachEnd
Indicates the point in time or event at which an entity’s role or tenure as a head coach comes to an end.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a2e9780819081add547c760abc9 |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:13 p.m.