Triple
T3157483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA franchise |
E66018
|
entity |
| Predicate | mayRelocateTo |
P46679
|
FINISHED |
| Object | different city |
—
|
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: different city | Statement: [NBA franchise, mayRelocateTo, different city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayRelocateTo Context triple: [NBA franchise, mayRelocateTo, different city]
-
A.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
-
B.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
C.
relocatedDuring
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
D.
relocatedBetween
Indicates that an entity changed location from one place to another during a specified time interval or between two reference points.
-
E.
relocated
Indicates that an entity has moved or been moved from one location or position to another.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ec0da88190a83f3448ac76e98e |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada1e4f7288190a80a1672e458132d |
completed | March 8, 2026, 4:20 p.m. |
Created at: March 8, 2026, 3:05 p.m.