Triple
T33732473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Münster im Elsass |
E864308
|
entity |
| Predicate | liegtImTal |
P32883
|
FINISHED |
| Object | Vallée de Munster |
—
|
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: Vallée de Munster | Statement: [Münster im Elsass, liegtImTal, Vallée de Munster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liegtImTal Context triple: [Münster im Elsass, liegtImTal, Vallée de Munster]
-
A.
liesBelow
Indicates that one entity is positioned at a lower vertical level than another entity.
-
B.
liesBetweenValleys
Indicates that something is positioned in the area or region separating two valleys.
-
C.
liegtAm
Indicates that one entity is located on, by, or along another entity (such as a place lying on a river, coast, or route).
-
D.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
-
E.
liesIn
chosen
Indicates that one entity is located within the spatial, geographical, or conceptual boundaries of another entity.
- F. None of above.
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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:44 a.m.