Triple
T36510644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Untersteinach |
E899893
|
entity |
| Predicate | locatedInStateType |
P13794
|
FINISHED |
| Object | federal state of Bavaria |
—
|
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: federal state of Bavaria | Statement: [Untersteinach, locatedInStateType, federal state of Bavaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInStateType Context triple: [Untersteinach, locatedInStateType, federal state of Bavaria]
-
A.
locatedInStateOrRegion
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
B.
housedInState
Indicates that an entity is located or situated within the boundaries of a particular state.
-
C.
locatedInFederalEntity
chosen
Indicates that one entity is geographically or administratively situated within the jurisdiction or boundaries of a specified federal entity.
-
D.
locatedInFormerState
Indicates that an entity is or was geographically situated within the boundaries of a political state that no longer exists in its former form.
-
E.
locatedInIndianState
Indicates that one entity is geographically situated within the boundaries of a specific Indian state.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.