Triple
T9675983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lentekhi |
E234152
|
entity |
| Predicate | roadTypeAccess |
P1019
|
FINISHED |
| Object | mountain road |
—
|
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: mountain road | Statement: [Lentekhi, roadTypeAccess, mountain road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadTypeAccess Context triple: [Lentekhi, roadTypeAccess, mountain road]
-
A.
roadAccessVia
Indicates that one location or area is reachable from another specifically by using a particular road or road segment.
-
B.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
roadAccessFrom
Indicates that one location can be reached from another via a usable road connection.
-
D.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
E.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6ed62081908863f2ea0e98961a |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.