Triple
T9487297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna Woods |
E228792
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Schöpfl |
E801719
|
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: Schöpfl | Statement: [Vienna Woods, contains, Schöpfl]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Schöpfl Context triple: [Vienna Woods, contains, Schöpfl]
-
A.
Schöpfl
chosen
Schöpfl is a prominent mountain in Lower Austria known as the highest peak of the Vienna Woods range.
-
B.
Schöngarth
Schöngarth is a German surname most notably associated with Eberhard Schöngarth, a high-ranking Nazi SS officer and war criminal during World War II.
-
C.
Pfäfers
Pfäfers is a Swiss municipality in the canton of St. Gallen, known for its historic Benedictine monastery and scenic location in the Tamina valley.
-
D.
Bramsche
Bramsche is a town in Lower Saxony, Germany, known for its location near Osnabrück and its historical textile industry.
-
E.
Fuhlenbrock
Fuhlenbrock is a residential district of the city of Bottrop in North Rhine-Westphalia, Germany.
- 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_69ca847424f081908180305555139f7a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd8051303881909566126a2688e41c |
completed | April 1, 2026, 8:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d139fdaccc8190b5c160aedcfcceca |
completed | April 4, 2026, 4:19 p.m. |
Created at: March 30, 2026, 7:55 p.m.