Triple
T31564637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frontenhausen |
E805372
|
entity |
| Predicate | regionCodeLevel1 |
P68047
|
FINISHED |
| Object | DE-BY |
E624970
|
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: DE-BY | Statement: [Frontenhausen, regionCodeLevel1, DE-BY]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionCodeLevel1 Context triple: [Frontenhausen, regionCodeLevel1, DE-BY]
-
A.
regionCodeLevel
chosen
Indicates the hierarchical level or granularity associated with a given regional code within an administrative or geographic coding system.
-
B.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
C.
regionCodeUsedIn
Indicates that a specific region code is utilized or applied within a particular context, system, or entity.
-
D.
regionCodeMeaning
Indicates that a region code is associated with its corresponding descriptive meaning or label.
-
E.
countrySubdivisionServed
Indicates a relationship where a service, organization, or entity operates within and provides its offerings to a specific administrative region or subdivision of a country.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d9958648190ac665cda29576a2c |
completed | June 11, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 30, 2026, 10:16 p.m.