Triple
T35402097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebuilding Ball State football program |
E1023261
|
entity |
| Predicate | startCoachTenure |
P202348
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Rebuilding Ball State football program, startCoachTenure, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startCoachTenure Context triple: [Rebuilding Ball State football program, startCoachTenure, 2003]
-
A.
endCoachTenure
Indicates that a coach’s period of service or employment with a team or organization has concluded.
-
B.
coachTenureIncludes
Indicates that a coach’s period of service or employment with a team or organization covers or includes a specified time span or event.
-
C.
yearsActiveAsCoach
Indicates the span of time, typically in years, during which an individual has served in a coaching role.
-
D.
teamTenure
Indicates the duration or length of time an entity has been part of a particular team.
-
E.
headCoachTenure
Indicates the duration or period during which a specific individual serves as the head coach of a team or organization.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0075be7f54819081ab12bc1dab53bb |
completed | May 10, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_6a0073a19030819098c23faa3adcb96e |
completed | May 10, 2026, 12:01 p.m. |
| PDg | Predicate description generation | batch_6a0075bd35e08190b604777ae9fbbe4b |
completed | May 10, 2026, 12:10 p.m. |
Created at: May 3, 2026, 4:03 p.m.