Triple
T15187861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MYK |
E362923
|
entity |
| Predicate | administrativeDistrictType |
P92063
|
FINISHED |
| Object | Landkreis |
—
|
LITERAL 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: Landkreis | Statement: [MYK, administrativeDistrictType, Landkreis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeDistrictType Context triple: [MYK, administrativeDistrictType, Landkreis]
-
A.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
B.
administrativeTerritoryType
chosen
Indicates the classification of an administrative area according to its level or type of territorial governance (e.g., city, county, province).
-
C.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
D.
usesAdministrativeDivisionType
Indicates that one entity employs or applies a particular type of administrative division as part of its territorial or organizational structure.
-
E.
typeOfDistrict
Indicates the specific category or classification to which a given district belongs.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067995fc8190b048f15086bd42f0 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:09 a.m.