Triple
T16355254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edward Jones Dome |
E397159
|
entity |
| Predicate | RamsRelocation |
P77279
|
FINISHED |
| Object | Rams moved to Los Angeles in 2016 |
—
|
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: Rams moved to Los Angeles in 2016 | Statement: [Edward Jones Dome, RamsRelocation, Rams moved to Los Angeles in 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RamsRelocation Context triple: [Edward Jones Dome, RamsRelocation, Rams moved to Los Angeles in 2016]
-
A.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
B.
teamRelocationEvent
chosen
Indicates an event in which a team changes its home location from one place to another.
-
C.
teamRelocatedResult
Indicates that a sports team has changed its home location and specifies the outcome or status resulting from that relocation.
-
D.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
E.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2face3a54819099418edd0eecc963 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:07 a.m.