Triple
T18417142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL on ABC |
E441921
|
entity |
| Predicate | returnedToAir |
P120524
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [NHL on ABC, returnedToAir, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToAir Context triple: [NHL on ABC, returnedToAir, 2021]
-
A.
wasReturnedTo
Indicates that an entity was sent or brought back to a previous owner, location, or state after having been away or removed.
-
B.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
C.
returnedToFlightStatus
Indicates that an entity previously grounded, inactive, or suspended has been restored to an approved or operational flight status.
-
D.
returnedToUse
chosen
Indicates that something previously inactive, unavailable, or discontinued has been put back into active use or operation.
-
E.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a284b608190b77c360a72aceb7a |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.