Triple
T6856043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiders |
E158145
|
entity |
| Predicate | relocationToLasVegasAnnounced |
P27085
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Raiders, relocationToLasVegasAnnounced, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationToLasVegasAnnounced Context triple: [Raiders, relocationToLasVegasAnnounced, 2017]
-
A.
relocationToLasVegasYear
chosen
Indicates the year in which an entity relocated to Las Vegas.
-
B.
relocationAnnouncedBy
Indicates that the relocation of something (such as a person, organization, or asset) was publicly communicated or made known by a particular agent or source.
-
C.
franchiseRelocatedFrom
Indicates that a sports or business franchise has moved its operations or home base away from a specified previous location.
-
D.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
E.
relocationToHouston
Indicates a change of location in which an entity moves or is transferred to Houston as its new place of residence or operation.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:20 p.m.