Triple
T16755147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Road to Taos |
E407187
|
entity |
| Predicate | approximateEndPoint |
P8204
|
FINISHED |
| Object | Taos area |
—
|
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: Taos area | Statement: [High Road to Taos, approximateEndPoint, Taos area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEndPoint Context triple: [High Road to Taos, approximateEndPoint, Taos area]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
hasApproximateEnd
chosen
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
C.
nearestPointTo
Indicates the point that is closest in distance to a given reference point or object among a set of candidates.
-
D.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
E.
approximateDirection
Indicates that one entity is located in a general or rough directional relation (e.g., roughly north, south, etc.) relative to another entity, without specifying an exact bearing.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3abe6b68c8190a5e2a11973f01b8e |
completed | April 18, 2026, 4:05 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.