Triple
T34915568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nossob 4x4 eco-trails |
E1006989
|
entity |
| Predicate | drivingSurface |
P101783
|
FINISHED |
| Object | sand tracks |
—
|
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: sand tracks | Statement: [Nossob 4x4 eco-trails, drivingSurface, sand tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingSurface Context triple: [Nossob 4x4 eco-trails, drivingSurface, sand tracks]
-
A.
laneSurface
chosen
Indicates the type or condition of the surface that makes up a lane used for travel or traffic.
-
B.
isSurfaceRoad
Indicates that a road segment is a surface-level street (not a highway, freeway, or limited-access road).
-
C.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
laneCondition
Indicates the state or quality of a lane, such as its usability, surface condition, or any factors affecting how it can be used.
- 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.