Triple
T23768930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kreis Riesa |
E587467
|
entity |
| Predicate | stateAfterReunification |
P123718
|
FINISHED |
| Object | Saxony |
—
|
NE NERFINISHED |
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 | Statement: [Kreis Riesa, stateAfterReunification, Saxony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateAfterReunification Context triple: [Kreis Riesa, stateAfterReunification, Saxony]
-
A.
statusAfterGermanReunification
chosen
Indicates the condition or state of an entity following the political reunification of Germany.
-
B.
reunificationStatus
Indicates the current state or outcome of efforts to bring previously separated entities back together into a single unified whole.
-
C.
confederationOfGermany
Indicates a relationship in which an entity is part of, associated with, or constitutes the Confederation of Germany as a political union or alliance.
-
D.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
E.
countryBefore1945
Indicates that one country existed or held a particular status in relation to another country before the year 1945.
- 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_69e2490b8ac48190a6b35f1d5500486b |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46507708190b0beba7f2b4d0bca |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:15 p.m.