Triple
T8292311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saquish Neck |
E193928
|
entity |
| Predicate | hasRoadAccessCharacteristic |
P55348
|
FINISHED |
| Object | limited access |
—
|
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: limited access | Statement: [Saquish Neck, hasRoadAccessCharacteristic, limited access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadAccessCharacteristic Context triple: [Saquish Neck, hasRoadAccessCharacteristic, limited access]
-
A.
isRoadAccessible
Indicates that a road can be safely and legally used or traversed under the current conditions.
-
B.
hasAccessRoadType
chosen
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
C.
hasNoDirectRoadAccess
Indicates that there is no direct road connection available between the relevant locations or entities.
-
D.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
E.
hasRoadway
Indicates that one location or area is connected to another by a road or roadway infrastructure.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c9ccbfc81908825685c23b80d23 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.