Triple
T35564340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2012–13 NHL season |
E1027726
|
entity |
| Predicate | lockoutEndDate |
P30927
|
FINISHED |
| Object | 2013-01-06 |
—
|
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: 2013-01-06 | Statement: [2012–13 NHL season, lockoutEndDate, 2013-01-06]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockoutEndDate Context triple: [2012–13 NHL season, lockoutEndDate, 2013-01-06]
-
A.
validityPeriodEnd
Indicates the date and time at which a previously valid state, authorization, or condition ceases to be valid.
-
B.
grantPeriodEnd
Indicates the date or point in time when a grant’s active period or eligibility officially ends.
-
C.
holderEndDate
Indicates the date on which an entity’s role as holder of something (e.g., an asset, position, or right) comes to an end.
-
D.
banPeriodEnd
chosen
Indicates the point in time when a ban or prohibition on an entity or action is scheduled to end.
-
E.
endAt
Indicates that an event, process, or state concludes or terminates at a specified time, location, or condition.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.