Triple
T4671654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mürren |
E102976
|
entity |
| Predicate | hasNoDirectRoadAccess |
P58770
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Mürren, hasNoDirectRoadAccess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoDirectRoadAccess Context triple: [Mürren, hasNoDirectRoadAccess, true]
-
A.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
-
B.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
C.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
D.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
E.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
- F. None of above. chosen
Provenance (4 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd655719dc8190beb6942f343a0ae7 |
completed | March 20, 2026, 3:18 p.m. |
Created at: March 20, 2026, 1:15 p.m.