Triple
T12125427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Forces/Air Defense of the NVA |
E288798
|
entity |
| Predicate | headquartersLocation |
P62
|
FINISHED |
| Object | Eggersdorf |
E686821
|
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: Eggersdorf | Statement: [Air Forces/Air Defense of the NVA, headquartersLocation, Eggersdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eggersdorf Context triple: [Air Forces/Air Defense of the NVA, headquartersLocation, Eggersdorf]
-
A.
Eggersdorf
chosen
Eggersdorf is a locality in eastern Germany known historically as the command center of the former East German Air Force.
-
B.
Ebersdorf
Ebersdorf is a historic town in present-day Germany that once served as the capital of one of the small Reuss principalities.
-
C.
Burkhardtsdorf
Burkhardtsdorf is a small municipality in the Erzgebirge (Ore Mountains) region of Saxony, eastern Germany.
-
D.
Eltersdorf
Eltersdorf is a district of the Bavarian city of Erlangen in Germany, known for its residential character and local transport connections.
-
E.
Euerdorf
Euerdorf is a small municipality in the Bavarian region of Lower Franconia in Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9157b2a9881908ec0e58cf438fce0 |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e48957081909c4598e82ab31e1f |
completed | May 2, 2026, 3:54 p.m. |
Created at: April 8, 2026, 9:49 p.m.