Triple
T25066341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference titles (NHL) |
E627792
|
entity |
| Predicate | rulesDefinedBy |
P125529
|
FINISHED |
| Object | NHL Rulebook |
—
|
NE NERFINISHED |
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: NHL Rulebook | Statement: [Western Conference titles (NHL), rulesDefinedBy, NHL Rulebook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rulesDefinedBy Context triple: [Western Conference titles (NHL), rulesDefinedBy, NHL Rulebook]
-
A.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
B.
rulesSystem
Indicates that an entity establishes, governs, or defines the rules or structure by which another system or process operates.
-
C.
scopeDefinedBy
Indicates that the extent or boundaries of one entity’s applicability, influence, or validity are determined or constrained by another entity.
-
D.
divisionDefinedBy
Indicates that a division or partition is established or characterized according to a specified rule, criterion, or defining entity.
-
E.
normDefinedBy
chosen
Indicates that a norm, rule, or standard is established, specified, or determined by a particular source or authority.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599e14688190aa19833f62ffb283 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:10 a.m.