Triple
T5609377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zac Taylor |
E147313
|
entity |
| Predicate | startTimeAsHeadCoachOfCincinnatiBengals |
P7574
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [Zac Taylor, startTimeAsHeadCoachOfCincinnatiBengals, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeAsHeadCoachOfCincinnatiBengals Context triple: [Zac Taylor, startTimeAsHeadCoachOfCincinnatiBengals, 2019]
-
A.
beganNFLHeadCoachingCareerWith
Indicates that an individual's first position as an NFL head coach was with the specified team.
-
B.
beganHeadCoachingCareerWith
Indicates that an individual started their head coaching career with a specified team or organization.
-
C.
headCoachOfClevelandBrownsEndYear
Indicates the year in which an individual's tenure as head coach of the Cleveland Browns ended.
-
D.
hiredAsHeadCoachYear
chosen
Indicates the year in which an individual was hired to serve as the head coach of a team or organization.
-
E.
endTimeAsHeadCoachOfJacksonvilleJaguars
Indicates the date and time when an individual’s tenure as head coach of the Jacksonville Jaguars ended.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fe7ee0819088ced51afd9a4f93 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.