Triple
T23428691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rax Alps |
E563263
|
entity |
| Predicate | hasAccessPoint |
P1985
|
FINISHED |
| Object | Payerbach |
E1491280
|
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: Payerbach | Statement: [Rax Alps, hasAccessPoint, Payerbach]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Payerbach Context triple: [Rax Alps, hasAccessPoint, Payerbach]
-
A.
Payerbach
chosen
Payerbach is a small Austrian town in Lower Austria known as a gateway to the Rax-Schneeberg mountain and hiking region.
-
B.
Gaisbach
Gaisbach is a village and district of the town of Oberkirch in the state of Baden-Württemberg in southwestern Germany.
-
C.
Kraichbach
Kraichbach is a small river in southwestern Germany that flows through the Kraichgau region before joining the Rhine.
-
D.
Schwabach
Schwabach is a historic town in northern Bavaria, Germany, known for its traditional gold-beating craft and well-preserved old town.
-
E.
Gentalbach
Gentalbach is a mountain stream in the Swiss Alps that flows through the Gental valley before joining the Hasli-Aare river system.
- 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_69e24553980c8190bb66a2ae0bdab125 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a54ba29881909945690496f28d65 |
completed | April 29, 2026, 6:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c82474ef88190b1e79a22471fae10 |
completed | May 19, 2026, 3:31 p.m. |
Created at: April 17, 2026, 5:48 p.m.