Triple
T27568093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regional Council of Vysočina |
E695956
|
entity |
| Predicate | hasCapitalOfRegion |
P135987
|
FINISHED |
| Object | Jihlava |
—
|
NE NERFINISHED |
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: Jihlava | Statement: [Regional Council of Vysočina, hasCapitalOfRegion, Jihlava]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCapitalOfRegion Context triple: [Regional Council of Vysočina, hasCapitalOfRegion, Jihlava]
-
A.
capitalLocatedInRegion
Indicates that a capital city is geographically situated within a specific region.
-
B.
countryCapitalOfRegion
Indicates that a country serves as the capital or primary governing state for a specified region.
-
C.
capitalOftenLocatedIn
Indicates that the capital city of a region or country is frequently, though not always, situated within a particular location or type of area.
-
D.
basedInCapital
Indicates that an entity is located or has its main base of operations in a capital city.
-
E.
endPointIsCapitalOf
chosen
Indicates that the endpoint entity serves as the capital city of the other related entity (typically a country, state, or region).
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 1:42 p.m.