Triple
T29774071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Murlen village |
E755327
|
entity |
| Predicate | hasAccessRoadTo |
P145268
|
FINISHED |
| Object | Murlen National Park |
—
|
NE NERFINISHED |
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: Murlen National Park | Statement: [Murlen village, hasAccessRoadTo, Murlen National Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessRoadTo Context triple: [Murlen village, hasAccessRoadTo, Murlen National Park]
-
A.
hasAccessRoadsTo
chosen
Indicates that there exist one or more roads providing direct vehicular access from one location or site to another.
-
B.
hasAccessRoadType
Indicates that an entity is connected to or served by a road of a specified access type (e.g., public, private, restricted).
-
C.
hasSeparateAccessRoadFor
Indicates that one entity is served by its own distinct access road that is separate from the access road used by another entity.
-
D.
hasRoadPass
Indicates that an entity possesses a valid authorization or permit required to use a specific road or road network.
-
E.
hasSeparateAccessRoad
Indicates that an entity is served by its own distinct access road, separate from other routes or shared entrances.
- 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_69f0ef878574819088c867fd1a5c8b86 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
Created at: April 28, 2026, 8:44 p.m.