Triple
T845010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wes Unseld |
E18257
|
entity |
| Predicate | teamTenure |
P20571
|
FINISHED |
| Object | 1968–1981 |
—
|
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: 1968–1981 | Statement: [Wes Unseld, teamTenure, 1968–1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamTenure Context triple: [Wes Unseld, teamTenure, 1968–1981]
-
A.
headCoachTenure
Indicates the duration or period during which a specific individual serves as the head coach of a team or organization.
-
B.
occupationDuration
Indicates the length of time an entity holds or has held a particular occupation or role.
-
C.
lifeTenure
Indicates that an individual holds a position or office for the duration of their lifetime, without a fixed term limit or routine reappointment.
-
D.
nflTeamTenure
Indicates the period of time that an individual was a member of a specific NFL team.
-
E.
activeYearsInCareer
Indicates the span of time during which an entity was actively engaged in a particular career or professional field.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac09249c8190a8099b94a3c9e2cc |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab4893e481908632102d240466dc |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:38 p.m.