Triple
T29373703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DON |
E744927
|
entity |
| Predicate | associatedDistrictCapital |
P15001
|
FINISHED |
| Object | Donauwörth |
E368758
|
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: Donauwörth | Statement: [DON, associatedDistrictCapital, Donauwörth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDistrictCapital Context triple: [DON, associatedDistrictCapital, Donauwörth]
-
A.
isDistrictCapitalOf
chosen
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
B.
countryCapitalDistrict
Indicates that a specified district serves as the capital district (administrative capital area) of a given country.
-
C.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified region.
-
D.
governingTerritorialCapital
Indicates that a territorial entity serves as the administrative or political capital for a governing body or jurisdiction.
-
E.
provinceHeadquarters
Indicates that one entity serves as the main administrative or organizational headquarters for a province associated with the other entity.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2863b20330819099d28758d671d671 |
completed | June 9, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: April 28, 2026, 2:29 p.m.