Triple
T31218879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Liones Drive trailhead |
E795944
|
entity |
| Predicate | trailLeadsToward |
P39694
|
FINISHED |
| Object | Parker Mesa Overlook |
—
|
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: Parker Mesa Overlook | Statement: [Los Liones Drive trailhead, trailLeadsToward, Parker Mesa Overlook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailLeadsToward Context triple: [Los Liones Drive trailhead, trailLeadsToward, Parker Mesa Overlook]
-
A.
trailBehavior
Indicates how an entity behaves, moves, or leaves traces along a path or trajectory over time.
-
B.
trailAssociation
chosen
Indicates an associative relationship between entities where one is contextually or functionally linked to a trail (such as being located on, connected to, or part of that trail).
-
C.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
-
D.
trailsBehind
Indicates that one entity follows or moves after another, remaining at a distance behind it in space, time, or progress.
-
E.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c4a700c81908ee61dcb01bffe50 |
completed | May 3, 2026, 12:52 a.m. |
| PD | Predicate disambiguation | batch_69f696673214819094350e1d2648ef34 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:10 p.m.