Triple
T33732483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Münster im Elsass |
E864308
|
entity |
| Predicate | hatRegion |
P285
|
FINISHED |
| Object | Elsass |
—
|
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: Elsass | Statement: [Münster im Elsass, hatRegion, Elsass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatRegion Context triple: [Münster im Elsass, hatRegion, Elsass]
-
A.
hasRegion
chosen
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
hitCapitalRegion
Indicates that an action, event, or impact has struck or affected the capital region of a specified area or jurisdiction.
-
C.
labelRegion
Indicates assigning a categorical or descriptive label to a specified region or area.
-
D.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
E.
houseRegion
Indicates that a house is located within or associated with a particular geographic or administrative region.
- 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.