Triple
T13945660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Gulls |
E335376
|
entity |
| Predicate | announcedRelocationToSanDiego |
P94305
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [San Diego Gulls, announcedRelocationToSanDiego, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedRelocationToSanDiego Context triple: [San Diego Gulls, announcedRelocationToSanDiego, 2015]
-
A.
renamedToSanFrancisco
Indicates that an entity’s name was changed to "San Francisco."
-
B.
movedToLosAngeles
Indicates that an entity changed their place of residence or primary location to Los Angeles.
-
C.
relocationAnnounced
chosen
Indicates that an official communication has been made stating that an entity will move from one location to another.
-
D.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
mayRelocateTo
Indicates that an entity has the possibility or permission to move or be moved from its current location to another 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e10f60c81908ee9636e85c070ff |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:17 p.m.