Triple
T22648103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Division (WHA) |
E559017
|
entity |
| Predicate | teamBaseCriterion |
P25634
|
FINISHED |
| Object | Canadian-based WHA franchises |
—
|
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: Canadian-based WHA franchises | Statement: [Canadian Division (WHA), teamBaseCriterion, Canadian-based WHA franchises]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamBaseCriterion Context triple: [Canadian Division (WHA), teamBaseCriterion, Canadian-based WHA franchises]
-
A.
teamBase
Indicates that one entity serves as the primary or foundational team associated with another entity.
-
B.
teamBasedOn
Indicates that one entity (typically a team) is formed, organized, or defined on the basis of another entity (such as a criterion, source, or underlying structure).
-
C.
teamLocationCriterion
chosen
Indicates a condition that specifies or restricts where a team must be located.
-
D.
clubBase
Indicates the location or place that serves as the primary base or home venue for a club.
-
E.
hasTeamBase
Indicates that a team is based at, or operates primarily from, a specific location or facility.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17039c2bc8190972a7c169b27005c |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.