Triple
T7465930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Angeles Dodgers–San Francisco Giants rivalry |
E176372
|
entity |
| Predicate | teamRelocationEvent |
P77279
|
FINISHED |
| Object | Brooklyn Dodgers relocation to Los Angeles in 1958 |
—
|
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: Brooklyn Dodgers relocation to Los Angeles in 1958 | Statement: [Los Angeles Dodgers–San Francisco Giants rivalry, teamRelocationEvent, Brooklyn Dodgers relocation to Los Angeles in 1958]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamRelocationEvent Context triple: [Los Angeles Dodgers–San Francisco Giants rivalry, teamRelocationEvent, Brooklyn Dodgers relocation to Los Angeles in 1958]
-
A.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
B.
teamRelocatedResult
Indicates that a sports team has changed its home location and specifies the outcome or status resulting from that relocation.
-
C.
teamRelocationYear
Indicates the year in which a team moved from one location to another.
-
D.
teamRelocationLeague
Indicates that a sports team has changed its home location while remaining within the same league.
-
E.
formerTeamRelocation
Indicates that an entity was previously associated with a team before that team relocated to a different place.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3f412908190ac910ecae682d6f6 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f386daac81908ded91b397b44148 |
completed | March 27, 2026, 9:15 p.m. |
Created at: March 27, 2026, 3:40 p.m.