Triple
T29519865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Stadium Cherkasy |
E748900
|
entity |
| Predicate | isMainStadiumOf |
P2439
|
FINISHED |
| Object | Cherkasy |
E205508
|
NE 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: Cherkasy | Statement: [Central Stadium Cherkasy, isMainStadiumOf, Cherkasy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainStadiumOf Context triple: [Central Stadium Cherkasy, isMainStadiumOf, Cherkasy]
-
A.
mainStadium
chosen
Indicates that a particular stadium serves as the primary or home stadium associated with an entity (such as a team, club, or organization).
-
B.
stadiumUsedFor
Indicates that a particular stadium is used for a specific activity, event, or purpose.
-
C.
mainStadiumLocatedIn
Indicates that the primary stadium associated with an entity is geographically situated within a specified location.
-
D.
countryNationalStadiumOf
Indicates that a given stadium serves as the official national stadium of a specified country.
-
E.
stadiumFor
Indicates that a particular stadium serves as the designated home or primary venue for a specific team, event, or organization.
- F. None of above.
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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34efef30408190a22ebbee8e61da34 |
completed | June 19, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 4:40 p.m.