Triple
T27763818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conters im Prättigau |
E701545
|
entity |
| Predicate | hasNeighboringEntityType |
P120316
|
FINISHED |
| Object | Swiss municipalities |
—
|
LITERAL 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: Swiss municipalities | Statement: [Conters im Prättigau, hasNeighboringEntityType, Swiss municipalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringEntityType Context triple: [Conters im Prättigau, hasNeighboringEntityType, Swiss municipalities]
-
A.
hasNeighbouringUnit
Indicates that one unit is directly adjacent to and shares a boundary or side with another unit.
-
B.
hasNeighboringFeature
Indicates that one feature is located adjacent to or directly next to another feature in space.
-
C.
hasNeighboringObject
Indicates that one object is located adjacent to or directly next to another object in space.
-
D.
hasNearbySiteType
chosen
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
-
E.
hasNeighboringSite
Indicates that one site is located adjacent to or directly next to another site.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 27, 2026, 4:29 p.m.