Triple
T34015138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camino Primitivo |
E872220
|
entity |
| Predicate | usesWaymark |
P47567
|
FINISHED |
| Object | yellow arrow |
—
|
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: yellow arrow | Statement: [Camino Primitivo, usesWaymark, yellow arrow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWaymark Context triple: [Camino Primitivo, usesWaymark, yellow arrow]
-
A.
waymarkingStatus
Indicates the current state or condition of a waymarking process, such as whether a location or route has been identified, recorded, approved, or otherwise classified in a waymarking system.
-
B.
trailsMarkedBy
chosen
Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
-
C.
hasWaypoint
Indicates that an entity follows a path or route that includes a specific intermediate location (waypoint) along its trajectory.
-
D.
hasMarkerOrMonument
Indicates that something possesses or is associated with a physical marker or monument commemorating it.
-
E.
isLandmarkFor
Indicates that one entity serves as a notable or significant reference point or attraction for another entity, such as a place, route, or area.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.