Triple
T22770308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goms |
E563536
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ulrichen |
—
|
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: Ulrichen | Statement: [Goms, contains, Ulrichen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulrichen Context triple: [Goms, contains, Ulrichen]
-
A.
Ulrichen
chosen
Ulrichen is a small alpine village in the Swiss canton of Valais, known for its scenic mountain landscape and outdoor recreation opportunities.
-
B.
Ursberg
Ursberg is a municipality in the Bavarian region of Swabia in southern Germany, known for its rural character and historical monastery complex.
-
C.
Ueffeln
Ueffeln is a village-level subdivision of the town of Bramsche in Lower Saxony, Germany.
-
D.
Ulrichstein
Ulrichstein is a small town in the Vogelsberg region of Hesse, Germany, known for its elevated location and surrounding natural landscapes.
-
E.
Leuenberg
Leuenberg is a village in Switzerland known as the site where major European Protestant churches concluded the Leuenberg Agreement on church fellowship.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b5cea44819097290351da9c488d |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 3:27 p.m.