Triple
T6207258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Pölten |
E138778
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Mostviertel |
E228789
|
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: Mostviertel | Statement: [St. Pölten, region, Mostviertel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mostviertel Context triple: [St. Pölten, region, Mostviertel]
-
A.
Mostviertel
chosen
Mostviertel is a picturesque region in southwestern Lower Austria known for its rolling hills, orchards, and traditional pear cider (Most) production.
-
B.
Innviertel
Innviertel is a historical and cultural region in western Upper Austria known for its rural landscapes, Baroque architecture, and strong Bavarian influences.
-
C.
Bettlach
Bettlach is a Swiss municipality located in the canton of Solothurn.
-
D.
Waldegg
Waldegg is a locality in Switzerland situated along the route of the A3 motorway.
-
E.
Oberegg
Oberegg is a Swiss municipality in the canton of Appenzell Innerrhoden, known for its rural landscape and location in the Appenzell region.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06270b8d08190a81bc03c8175b989 |
completed | March 22, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d1171788190aa302b54d14e9a5d |
completed | March 27, 2026, 7:09 a.m. |
Created at: March 22, 2026, 4:20 p.m.