Triple
T926386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Jersey Devils |
E19991
|
entity |
| Predicate | divisionChampionships |
P549
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [New Jersey Devils, divisionChampionships, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionChampionships Context triple: [New Jersey Devils, divisionChampionships, 9]
-
A.
divisionTitles
chosen
Indicates that an entity holds or is associated with one or more titles or championships within a specific division or category.
-
B.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
C.
divisionRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
-
D.
topDivision
Indicates that an entity belongs to the highest-level division or tier within a hierarchical structure.
-
E.
championshipSeries
Indicates a competitive series of contests or games that determines a champion between qualifying participants.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2970a4c8190b22cb2fd4706f62b |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.