Triple
T22003120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augsburg Airport |
E543381
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Affing |
—
|
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: Affing | Statement: [Augsburg Airport, locatedIn, Affing]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Affing Context triple: [Augsburg Airport, locatedIn, Affing]
-
A.
Affing
chosen
Affing is a small municipality in the district of Aichach-Friedberg in Bavaria, Germany, known for its rural character and proximity to the city of Augsburg.
-
B.
Faimingen
Faimingen is a village and district of the town of Lauingen in the Bavarian region of Germany, known for its rural character and local community life.
-
C.
Beaufays
Beaufays is a village in the municipality of Chaudfontaine in the province of Liège, Belgium.
-
D.
Finnebach
Finnebach is a small river in Germany that serves as a tributary of the Unstrut.
-
E.
Houffalize
Houffalize is a small town in the Belgian Ardennes known for its World War II history, outdoor tourism, and scenic natural surroundings.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1276cab5c8190ac1236fde7e0394a |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 16, 2026, 8:20 p.m.