Triple
T37280516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leutesheim |
E925373
|
entity |
| Predicate | regionalDistrictSeat |
P15001
|
FINISHED |
| Object | Offenburg |
—
|
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: Offenburg | Statement: [Leutesheim, regionalDistrictSeat, Offenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalDistrictSeat Context triple: [Leutesheim, regionalDistrictSeat, Offenburg]
-
A.
isDistrictCapitalOf
chosen
Indicates that a location serves as the administrative or governmental capital of a specified district.
-
B.
municipalitySeat
Indicates that one entity serves as the administrative center or capital (seat) of a municipality.
-
C.
capitalCityOfRegion
Indicates that a city serves as the official capital of a specified region, functioning as its primary administrative or governmental center.
-
D.
capitalOfSubdivision
Indicates that a place serves as the administrative capital of a specified subnational division (such as a state, province, or region).
-
E.
capitalOfReferencedRegion
Indicates that one entity serves as the capital city or administrative center of the region referenced by another entity.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
Created at: May 3, 2026, 4:16 p.m.