Triple
T27119544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver Warriors |
E686956
|
entity |
| Predicate | relocatedToVancouver |
P1660
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Vancouver Warriors, relocatedToVancouver, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocatedToVancouver Context triple: [Vancouver Warriors, relocatedToVancouver, 2014]
-
A.
relocatedToGuelph
Indicates that an entity has moved its residence, operations, or primary location to Guelph.
-
B.
movedToLosAngeles
Indicates that an entity changed their place of residence or primary location to Los Angeles.
-
C.
relocatedTo
chosen
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
D.
renamedToSanFrancisco
Indicates that an entity’s name was changed to "San Francisco."
-
E.
relocatedCompanyHeadquartersTo
Indicates that a company moved its main headquarters from a previous location to a new specified location.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f624421d188190a5356a4596df536e |
completed | May 2, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:58 a.m.