Triple
T8016613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazan International Airport |
E186632
|
entity |
| Predicate | renovatedForEvent |
P3322
|
FINISHED |
| Object | 2013 Summer Universiade |
—
|
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: 2013 Summer Universiade | Statement: [Kazan International Airport, renovatedForEvent, 2013 Summer Universiade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renovatedForEvent Context triple: [Kazan International Airport, renovatedForEvent, 2013 Summer Universiade]
-
A.
venueRebuilt
Indicates that a venue has been reconstructed or significantly renovated after a prior state of damage, disuse, or demolition.
-
B.
renovatedAfter
Indicates that one entity was renovated at a later time than another entity.
-
C.
renovatedBy
Indicates that an entity has been improved, restored, or updated through renovation work performed by another entity.
-
D.
homeArenaRenovated
Indicates that the team's primary home arena has undergone renovation or significant upgrades.
-
E.
hasRenovation
chosen
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df37a00819088780e5461bc5b41 |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.