Triple
T37011678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver Blazers |
E915965
|
entity |
| Predicate | cityAlsoHasTeam |
P45971
|
FINISHED |
| Object | Vancouver Canucks |
—
|
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: Vancouver Canucks | Statement: [Vancouver Blazers, cityAlsoHasTeam, Vancouver Canucks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityAlsoHasTeam Context triple: [Vancouver Blazers, cityAlsoHasTeam, Vancouver Canucks]
-
A.
homeCityTeamOf
Indicates that one entity is the sports team based in and representing the home city of the other entity.
-
B.
cityInLeague
Indicates that a city is a member of, or participates in, a particular league or organized association.
-
C.
cityTeam2
Indicates that a team is based in, represents, or is associated with a particular city.
-
D.
cityOfFictionalTeam
Indicates the city in which a fictional sports team is based or represents.
-
E.
successorTeamInCity
chosen
Indicates that one team is the direct replacement or continuation of another team within the same city.
- 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_69f76e90ed548190b187d2475f5c807d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.