Triple
T3046559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MON |
E83462
|
entity |
| Predicate | teamHeritage |
P36696
|
FINISHED |
| Object | historic NHL franchise |
—
|
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: historic NHL franchise | Statement: [MON, teamHeritage, historic NHL franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamHeritage Context triple: [MON, teamHeritage, historic NHL franchise]
-
A.
teamHonors
Indicates that a team has received a particular honor, award, or title.
-
B.
teamRepresentation
Indicates that one entity serves as the official representative or embodiment of a team in a given context or activity.
-
C.
sportsHeritage
chosen
Indicates a relationship where one entity preserves, represents, or is associated with the historical traditions, legacy, or cultural heritage of a sport or sporting community.
-
D.
nationalTeamSystem
Indicates a relationship where an entity is part of, governed by, or operates within a specific national team structure or organizational system.
-
E.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bab541c8190a17aca26b3dcfae7 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.