Triple
T34006726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inner Basin Trail |
E871985
|
entity |
| Predicate | hasStartPointNear |
P118122
|
FINISHED |
| Object | Lockett Meadow |
—
|
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: Lockett Meadow | Statement: [Inner Basin Trail, hasStartPointNear, Lockett Meadow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStartPointNear Context triple: [Inner Basin Trail, hasStartPointNear, Lockett Meadow]
-
A.
hasNearbyPoint
chosen
Indicates that one entity has at least one other point located within a specified proximity or distance from it.
-
B.
startPointLocatedIn
Indicates that the starting point of something is geographically or spatially located within a specified area or region.
-
C.
hasNearbyCrossingPoint
Indicates that one location has a crossing point (such as a bridge, crosswalk, or intersection) situated close to it.
-
D.
nearestPointTo
Indicates the point that is closest in distance to a given reference point or object among a set of candidates.
-
E.
hasStopNear
Indicates that one entity has a stop or stopping point located in close proximity to another entity.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 1, 2026, 1:50 a.m.