Triple
T34165485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OG |
E876397
|
entity |
| Predicate | registrationCodeForDistrictSeat |
P178470
|
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: [OG, registrationCodeForDistrictSeat, Offenburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registrationCodeForDistrictSeat Context triple: [OG, registrationCodeForDistrictSeat, Offenburg]
-
A.
adminDistrictSeat
Indicates that one entity serves as the administrative center or capital seat of an administrative district to which the other entity belongs.
-
B.
districtCode
Indicates that an entity is associated with, or identified by, a specific administrative district code.
-
C.
regionForPRSeats
Indicates the geographic or administrative region associated with a set of proportional representation (PR) seats.
-
D.
sourceDistrict
Indicates the district from which something originates, is sent, or is sourced.
-
E.
hasCityDistrictCode
Indicates that a city district is associated with a specific identifying code.
- F. None of above. chosen
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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:54 a.m.