Triple
T1033873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose Earthquakes |
E22314
|
entity |
| Predicate | relocationToHouston |
P23901
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [San Jose Earthquakes, relocationToHouston, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationToHouston Context triple: [San Jose Earthquakes, relocationToHouston, 2005]
-
A.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
B.
reasonForRelocation
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
C.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
-
D.
relocatedFrom
Indicates that an entity has moved or been transferred away from a specified original location.
-
E.
relocatedToWashingtonYear
Indicates the year in which an entity moved or was transferred to Washington as its new location.
- F. None of above. chosen
Provenance (4 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8d669448190955507e2e4975b9f |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b728ad3481909cf1430349cb9bba |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8d5076481908640a0d873efdf14 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:41 p.m.