Triple
T37439501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dudh Dhara Falls |
E930374
|
entity |
| Predicate | hasLocalTransportAccess |
P160825
|
FINISHED |
| Object | road access up to nearby point then walk |
—
|
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: road access up to nearby point then walk | Statement: [Dudh Dhara Falls, hasLocalTransportAccess, road access up to nearby point then walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalTransportAccess Context triple: [Dudh Dhara Falls, hasLocalTransportAccess, road access up to nearby point then walk]
-
A.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
B.
hasNearbyAccess
Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
-
C.
hasLocalSupport
Indicates that an entity receives backing, endorsement, or assistance from people or organizations within its immediate geographic or community area.
-
D.
hasTransportationProximityTo
chosen
Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
-
E.
hasNearbyPortAccess
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff8ba3f8248190bbdf8e7ec2b35093 |
completed | May 9, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69ff8b41ba988190a7332e8317d10f09 |
completed | May 9, 2026, 7:30 p.m. |
Created at: May 3, 2026, 4:17 p.m.