Triple
T2985341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XIV Olympiad |
E80610
|
entity |
| Predicate | constructionOfNewVenues |
P44481
|
FINISHED |
| Object | minimal due to post-war austerity |
—
|
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: minimal due to post-war austerity | Statement: [XIV Olympiad, constructionOfNewVenues, minimal due to post-war austerity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionOfNewVenues Context triple: [XIV Olympiad, constructionOfNewVenues, minimal due to post-war austerity]
-
A.
futureStadiumProject
Indicates a planned or proposed stadium development that is intended to be built or realized in the future.
-
B.
sportsVenueFor
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
C.
openedAsSportsVenue
Indicates that a place or facility began its operation specifically for hosting sports events or activities.
-
D.
venueComplex
Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
-
E.
stadium
Indicates that an entity is a sports or event venue where games, competitions, or large gatherings take 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c65ad0819087bb4ae92ab0dc55 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f5d28c8190899d90204dc43428 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 2:59 p.m.