Triple
T3652455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS |
E77449
|
entity |
| Predicate | adminRegionLevel |
P6712
|
FINISHED |
| Object | Kreisfreie Stadt (independent city) |
—
|
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: Kreisfreie Stadt (independent city) | Statement: [OS, adminRegionLevel, Kreisfreie Stadt (independent city)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adminRegionLevel Context triple: [OS, adminRegionLevel, Kreisfreie Stadt (independent city)]
-
A.
arealRegion
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
-
B.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
C.
latitudeRegion
Indicates that an entity is located within, or associated with, a specific geographic region defined by latitude coordinates.
-
D.
jurisdictionLevel
chosen
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3b664448190986b5223d59de282 |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.