Triple
T8631184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1990–91 NHL season |
E204404
|
entity |
| Predicate | expansionOrRelocation |
P84533
|
FINISHED |
| Object | no franchise relocations |
—
|
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: no franchise relocations | Statement: [1990–91 NHL season, expansionOrRelocation, no franchise relocations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionOrRelocation Context triple: [1990–91 NHL season, expansionOrRelocation, no franchise relocations]
-
A.
relocationResultedIn
Indicates that one relocation event caused or led to a particular outcome, state, or consequence.
-
B.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
C.
numberOfRelocations
Indicates the total count of times an entity has been moved or relocated from one place or position to another.
-
D.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
E.
expansionAlongside
Indicates that one entity expands or grows in parallel with, and in relation to, the expansion of another entity.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc572d99bc819097f36b140c2ee1ce |
completed | March 31, 2026, 11:22 p.m. |
Created at: March 30, 2026, 6:27 p.m.