Triple
T5376298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas City Royals–Minnesota Twins rivalry |
E108967
|
entity |
| Predicate | team2RelocatedToMinnesota |
P46928
|
FINISHED |
| Object | 1961 |
—
|
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: 1961 | Statement: [Kansas City Royals–Minnesota Twins rivalry, team2RelocatedToMinnesota, 1961]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2RelocatedToMinnesota Context triple: [Kansas City Royals–Minnesota Twins rivalry, team2RelocatedToMinnesota, 1961]
-
A.
team2RelocatedToCurrentCity
Indicates that the second team has moved its location to the city where it is currently based.
-
B.
teamRelocatedFrom
Indicates that a team previously based in one location has moved its home base or operations from that original location to a different one.
-
C.
teamRelocationTo
Indicates the movement of a team from one location to another as its new home or base of operations.
-
D.
team2RelocationYear
chosen
Indicates the year in which the second team in a relationship was relocated to a different place or franchise.
-
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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.