Triple
T2910494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnipeg Jets (2011–present) |
E63670
|
entity |
| Predicate | captainTenureStart |
P14551
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Winnipeg Jets (2011–present), captainTenureStart, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainTenureStart Context triple: [Winnipeg Jets (2011–present), captainTenureStart, 2016]
-
A.
captaincyStartYear
Indicates the year in which an entity first assumed the role of captain.
-
B.
captaincyEndYear
Indicates the year in which an entity’s period of serving as captain comes to an end.
-
C.
heritageDesignationStartTime
Indicates the point in time when an entity was officially granted a particular heritage designation.
-
D.
teamCaptainStartYear
chosen
Indicates the year in which an entity first began serving as the captain of a team.
-
E.
previousHolderStartDate
Indicates the date on which the immediately preceding holder of something (e.g., a position, title, or asset) began their tenure or ownership.
- 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_69ab4c44ab448190b9411324e8a1fc1d |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe0e899808190a348e1e71116d0a5 |
completed | March 7, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69abdd1b77608190b20fc078fdb85e64 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:11 p.m.