Triple
T4226342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truman Sports Complex |
E94466
|
entity |
| Predicate | separatedStadiumDesign |
P32066
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Truman Sports Complex, separatedStadiumDesign, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedStadiumDesign Context triple: [Truman Sports Complex, separatedStadiumDesign, yes]
-
A.
stadiumFeature
chosen
Indicates that a stadium possesses or includes a particular feature, characteristic, or facility.
-
B.
stadium
Indicates that an entity is a sports or event venue where games, competitions, or large gatherings take place.
-
C.
sharedStadiumRegion
Indicates that two or more entities use stadiums located within the same geographic region.
-
D.
mainStadium
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
E.
secondaryStadium
Indicates that an entity serves as an additional or backup stadium associated with another primary stadium or team.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4ed34c819081d1479ce87cd78c |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.