Triple
T1861174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Hockey League |
E34814
|
entity |
| Predicate | featuredCrossBorderTeams |
P33196
|
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: [International Hockey League, featuredCrossBorderTeams, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredCrossBorderTeams Context triple: [International Hockey League, featuredCrossBorderTeams, true]
-
A.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
B.
integratedTeam
Indicates that multiple parties work together as a single, coordinated unit with shared goals, processes, and responsibilities.
-
C.
attractsTeamsFrom
Indicates that an entity draws or pulls in teams from another specified entity or location.
-
D.
regionTeam
Indicates that a team is associated with, operates in, or represents a specific geographic region.
-
E.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb16a6db48190af04012e8ed2269f |
completed | March 7, 2026, 5:02 a.m. |
Created at: March 4, 2026, 7:34 p.m.