Triple
T419993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Conference (NHL) |
E8079
|
entity |
| Predicate | teamsRegion |
P1015
|
FINISHED |
| Object | eastern North America |
—
|
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: eastern North America | Statement: [Eastern Conference (NHL), teamsRegion, eastern North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamsRegion Context triple: [Eastern Conference (NHL), teamsRegion, eastern North America]
-
A.
sportsRegionOf
chosen
Indicates that a region is the geographic or administrative area associated with a particular sports entity or activity.
-
B.
countryRegion
Indicates that a country is located within, or belongs to, a specific geographic or administrative region.
-
C.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
D.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
-
E.
regionName
Indicates the name assigned to a specific geographic or administrative region.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eebde1d881908fb212bfba9d7c67 |
completed | Feb. 28, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69a2edd3b948819097d96c73d0a0f699 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.