Triple
T10172326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baden District |
E235360
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ebreichsdorf |
E783151
|
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: Ebreichsdorf | Statement: [Baden District, contains, Ebreichsdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ebreichsdorf Context triple: [Baden District, contains, Ebreichsdorf]
-
A.
Ebreichsdorf
chosen
Ebreichsdorf is a small town in Lower Austria known for its equestrian facilities and proximity to Vienna.
-
B.
Kiliansdorf
Kiliansdorf is a village and district of the town of Roth in the Bavarian region of Germany.
-
C.
Gumpoldskirchen
Gumpoldskirchen is a historic wine-growing town in Lower Austria, renowned for its traditional vineyards and picturesque setting near Vienna.
-
D.
Ebersdorf
Ebersdorf is a historic town in present-day Germany that once served as the capital of one of the small Reuss principalities.
-
E.
Beckenried
Beckenried is a Swiss lakeside municipality and village situated on the shores of Lake Lucerne in the canton of Nidwalden.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec9f6dd8819081588600499165ee |
completed | April 2, 2026, 4:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3178844c48190af952ac30a4d6d97 |
completed | April 6, 2026, 2:16 a.m. |
Created at: March 30, 2026, 9:10 p.m.