Triple
T32879497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aprath |
E841016
|
entity |
| Predicate | regionalGovernmentDistrict |
P128478
|
FINISHED |
| Object | Düsseldorf (Regierungsbezirk) |
—
|
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: Düsseldorf (Regierungsbezirk) | Statement: [Aprath, regionalGovernmentDistrict, Düsseldorf (Regierungsbezirk)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalGovernmentDistrict Context triple: [Aprath, regionalGovernmentDistrict, Düsseldorf (Regierungsbezirk)]
-
A.
governmentalDistrictOf
chosen
Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
-
B.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
C.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
D.
districtRegion
Indicates that a district is located within or belongs administratively to a specific region.
-
E.
isProvincialDistrictOf
Indicates that one administrative district belongs to, or is governed as part of, a specific province.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 1, 2026, 1:18 a.m.