Triple
T25602027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007 NHL All-Star Game |
E641811
|
entity |
| Predicate | returnedAfterHiatus |
P44197
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2007 NHL All-Star Game, returnedAfterHiatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedAfterHiatus Context triple: [2007 NHL All-Star Game, returnedAfterHiatus, true]
-
A.
releasedAfterHiatusOf
Indicates that one entity (typically a work or product) was released following a preceding break or hiatus of the other entity (such as an artist, series, or organization).
-
B.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
C.
returnedToLiveIn
Indicates that an entity moved back to a place where they had previously lived and resumed living there.
-
D.
resumedIn
chosen
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
E.
re-establishedAfter
Indicates that a relationship or state was previously ended or inactive and then brought back into effect following a specified event or time.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a7d7d881909014fdf3746f981b |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 4:31 p.m.