Triple
T1373930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Las Vegas Raiders |
E30176
|
entity |
| Predicate | relocationToLasVegasYear |
P27085
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Las Vegas Raiders, relocationToLasVegasYear, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationToLasVegasYear Context triple: [Las Vegas Raiders, relocationToLasVegasYear, 2020]
-
A.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
B.
relocatedToWashingtonYear
Indicates the year in which an entity moved or was transferred to Washington as its new location.
-
C.
relocationToHouston
Indicates a change of location in which an entity moves or is transferred to Houston as its new place of residence or operation.
-
D.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
E.
relocatedToMunichIn
Indicates that an entity moved its location to Munich in a specified year or time period.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f660888190bc9240e0dc4f0aa3 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befcabdc8190a9f05d002603f81c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0335f7081908d50046ced4cdee0 |
completed | March 1, 2026, 10:39 p.m. |
Created at: March 1, 2026, 7:57 p.m.