Triple
T527873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campbell Conference All-Stars |
E10961
|
entity |
| Predicate | opponentType |
P13136
|
FINISHED |
| Object | other NHL all-star teams |
—
|
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: other NHL all-star teams | Statement: [Campbell Conference All-Stars, opponentType, other NHL all-star teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentType Context triple: [Campbell Conference All-Stars, opponentType, other NHL all-star teams]
-
A.
decidingOpponent
Indicates that one entity is the opponent or counterpart responsible for making a decision that affects another entity.
-
B.
opponentNationality
Indicates that the related entity is the country or nationality of the opponent in a competitive or adversarial context.
-
C.
keyOpponents
chosen
Indicates that the subject has primary or most significant opponents identified by the object.
-
D.
opponentCandidate
Indicates that one entity is a rival or competing candidate against another in the same contest or election.
-
E.
opponentAtMidway
Indicates that one entity is the opposing side or competitor of another in the context of the Midway event, location, or stage.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d2851c81908129f7da932ab7b3 |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.