Triple
T5805199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haderslev |
E128727
|
entity |
| Predicate | regionCapitalRole |
P16248
|
FINISHED |
| Object | subregional administrative center |
—
|
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: subregional administrative center | Statement: [Haderslev, regionCapitalRole, subregional administrative center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCapitalRole Context triple: [Haderslev, regionCapitalRole, subregional administrative center]
-
A.
countryCapitalRole
Indicates that one entity serves as the capital city of a given country, representing its primary administrative or governmental center.
-
B.
regionCapital
chosen
Indicates that one entity is the capital city or administrative center of a specified region.
-
C.
capitalCityOfStateInRegion
Indicates that a city serves as the capital of a state that is located within a specified region.
-
D.
cityAsCapitalOf
Indicates that a city serves as the official capital of a specified political or administrative entity.
-
E.
countryCapitalRegion
Indicates that a specified region is the capital region (administrative capital area) of a given country.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02b1461a48190be2042dd3823d02e |
completed | March 22, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69c021d477008190946113f9859eeb90 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:52 p.m.