Triple
T10091938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iowa Hawkeyes wrestling team |
E215362
|
entity |
| Predicate | headCoachSince |
P7106
|
FINISHED |
| Object | 2006 |
—
|
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: 2006 | Statement: [Iowa Hawkeyes wrestling team, headCoachSince, 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headCoachSince Context triple: [Iowa Hawkeyes wrestling team, headCoachSince, 2006]
-
A.
headCoachStartYear
chosen
Indicates the year in which an individual began serving 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.
headCoachPreviousTenure
Indicates that a person served as the head coach of a team or organization during a prior period before the current tenure.
-
D.
hiredAsHeadCoachYear
Indicates the year in which an individual was hired to serve as the head coach of a team or organization.
-
E.
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.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05aa02081908fba02e7085c6d7c |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.