Triple
T24044840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Wild Horse Canyon |
E595487
|
entity |
| Predicate | trailMarked |
P47567
|
FINISHED |
| Object | partially, with signs near trailhead and junctions |
—
|
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: partially, with signs near trailhead and junctions | Statement: [Little Wild Horse Canyon, trailMarked, partially, with signs near trailhead and junctions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailMarked Context triple: [Little Wild Horse Canyon, trailMarked, partially, with signs near trailhead and junctions]
-
A.
trailsMarkedBy
chosen
Indicates that a trail or path is designated or identified by specific markers, signs, or blazes placed along its route.
-
B.
marked
Indicates that one entity has been identified, labeled, or highlighted in some way by another entity.
-
C.
usedToMark
Indicates that one entity serves as a marker, label, or indicator for another entity.
-
D.
seedMarking
Indicates that an entity bears or applies a specific mark, pattern, or label associated with seeds.
-
E.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9c9391c819095ea6232fa872d5c |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:11 p.m.