Triple
T23656588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stadion Kraj Bistrice |
E584317
|
entity |
| Predicate | locatedInCountryCapitalOf |
P5025
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Stadion Kraj Bistrice, locatedInCountryCapitalOf, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryCapitalOf Context triple: [Stadion Kraj Bistrice, locatedInCountryCapitalOf, no]
-
A.
locatedInCountryCapitalSystem
Indicates that an entity is situated in the capital city of a specified country within a country–capital relationship system.
-
B.
governingCountryCapitalLocatedIn
Indicates that the capital city of a governing country is geographically located within a specified territory or region.
-
C.
locatedInCapital
chosen
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
-
D.
locatedInCountryCapitalLanguage
Indicates that an entity is located in a country’s capital city where a specified language is used or officially recognized.
-
E.
locatedInCountryCapitalOfProvince
Indicates that an entity is located in the country that contains the capital city of a specified province.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b35c257c81909f7004c0a35be4e3 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.