Triple
T17678164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frankfurt Egelsbach Airport |
E440691
|
entity |
| Predicate | locatedInMunicipality |
P40
|
FINISHED |
| Object | Egelsbach |
—
|
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: Egelsbach | Statement: [Frankfurt Egelsbach Airport, locatedInMunicipality, Egelsbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Egelsbach Context triple: [Frankfurt Egelsbach Airport, locatedInMunicipality, Egelsbach]
-
A.
Egelsbach
chosen
Egelsbach is a municipality in the German state of Hesse, located between Frankfurt am Main and Darmstadt and known for its general aviation airfield.
-
B.
Eifgenbach
Eifgenbach is a small river in North Rhine-Westphalia, Germany, that flows through the Bergisches Land region before joining the Wupper.
-
C.
Eschbach
Eschbach is a village and district of the town of Usingen in the Hochtaunus region of Hesse, Germany.
-
D.
Buhlbach
Buhlbach is a small locality or district within the Black Forest municipality of Baiersbronn in southwestern Germany.
-
E.
Oberleichtersbach
Oberleichtersbach 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 (2 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6e959c819092d9d33e79bd51f7 |
completed | April 19, 2026, 6 a.m. |
Created at: April 10, 2026, 10:01 a.m.