Triple
T23944083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIRST Championship |
E602865
|
entity |
| Predicate | previouslyHostedIn |
P104984
|
FINISHED |
| Object | St. Louis, Missouri, United States |
—
|
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: St. Louis, Missouri, United States | Statement: [FIRST Championship, previouslyHostedIn, St. Louis, Missouri, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslyHostedIn Context triple: [FIRST Championship, previouslyHostedIn, St. Louis, Missouri, United States]
-
A.
hasBeenHostedIn
chosen
Indicates that an event, show, or activity took place or was conducted at a particular location or venue in the past.
-
B.
previouslyLocatedIn
Indicates that an entity was located in a particular place or region at some time in the past, but is not necessarily located there now.
-
C.
previouslyIn
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
-
D.
hasFormerHost
Indicates that an entity previously served as the host of another entity but no longer holds that hosting role.
-
E.
originallyHostedAt
Indicates the location or venue where something was first hosted or took place before any subsequent moves or changes.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02d07b08190acbcbb646cd9a58e |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:11 p.m.