Triple
T19197678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Świętokrzyskie |
E470013
|
entity |
| Predicate | hasRegionalCapitalStatus |
P54252
|
FINISHED |
| Object | Kielce |
—
|
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: Kielce | Statement: [Świętokrzyskie, hasRegionalCapitalStatus, Kielce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionalCapitalStatus Context triple: [Świętokrzyskie, hasRegionalCapitalStatus, Kielce]
-
A.
regionCapitalStatus
chosen
Indicates that one entity serves as the capital of a specified region or administrative area in relation to another entity.
-
B.
hasCountryCapitalStatus
Indicates that a location holds the official status of being the capital city of a specified country.
-
C.
hasCapitalRegionRelation
Indicates a relationship where one entity serves as the capital region or administrative capital area of another entity.
-
D.
hasCapitalDistrictStatus
Indicates that an administrative region holds the official status of being a capital district within a country or larger jurisdiction.
-
E.
isPlannedRegionalCapitalOf
Indicates that a location has been officially designated to become the regional capital in the future, but is not yet serving as the current regional capital.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f8a695cc8190b84a220f52c51dfc |
completed | April 20, 2026, 9:57 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:07 p.m.