Triple
T9339867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Stars–New York Rangers games |
E224736
|
entity |
| Predicate | conferenceMatchupType |
P87602
|
FINISHED |
| Object | inter-conference |
—
|
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: inter-conference | Statement: [Dallas Stars–New York Rangers games, conferenceMatchupType, inter-conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceMatchupType Context triple: [Dallas Stars–New York Rangers games, conferenceMatchupType, inter-conference]
-
A.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
B.
featuredMatchType
Indicates the specific category or kind of match that is highlighted or given special prominence.
-
C.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
D.
finalsMatchup
Indicates that two competitors or teams are paired to face each other in the final round of a competition or tournament.
-
E.
definingMatchup
Indicates a matchup that is especially significant or decisive in defining the outcome, narrative, or importance of a broader event or competition.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bae2e2481909effc2dc89a642c5 |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:40 p.m.