Triple
T24150682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreis Nebra |
E598521
|
entity |
| Predicate | partOfCurrentState |
P23956
|
FINISHED |
| Object | Saxony-Anhalt |
E48552
|
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: Saxony-Anhalt | Statement: [Kreis Nebra, partOfCurrentState, Saxony-Anhalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCurrentState Context triple: [Kreis Nebra, partOfCurrentState, Saxony-Anhalt]
-
A.
inState
chosen
Indicates that an entity is currently located within or belongs to a particular state or condition.
-
B.
innerState
Indicates a relationship where an entity’s internal condition, feeling, or mental/emotional status is specified or characterized.
-
C.
parentState
Indicates that one state serves as the immediate higher-level or containing state of another state within a hierarchical structure.
-
D.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
-
E.
principalState
Indicates that an entity serves as the primary or main state associated with another entity or context.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e108308190ba8740590a1c5130 |
completed | April 29, 2026, 10:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fe3386b0c81909009f53e1bd2cb9f |
completed | May 22, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.