Triple
T29363135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drillers Stadium |
E744644
|
entity |
| Predicate | teamMovedTo |
P36297
|
FINISHED |
| Object | ONEOK Field in downtown Tulsa |
—
|
NE NERFINISHED |
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: ONEOK Field in downtown Tulsa | Statement: [Drillers Stadium, teamMovedTo, ONEOK Field in downtown Tulsa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamMovedTo Context triple: [Drillers Stadium, teamMovedTo, ONEOK Field in downtown Tulsa]
-
A.
teamRelocationTo
chosen
Indicates the movement of a team from one location to another as its new home or base of operations.
-
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.
teamRelocatedResult
Indicates that a sports team has changed its home location and specifies the outcome or status resulting from that relocation.
-
D.
teamRelocationEvent
Indicates an event in which a team changes its home location from one place to another.
-
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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669894f608190941fed17608d9c2e |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:20 p.m.