Triple
T15571393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handies Peak |
E374249
|
entity |
| Predicate | standardRouteGain |
P119231
|
FINISHED |
| Object | approximately 2500 ft |
—
|
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: approximately 2500 ft | Statement: [Handies Peak, standardRouteGain, approximately 2500 ft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRouteGain Context triple: [Handies Peak, standardRouteGain, approximately 2500 ft]
-
A.
standardRouteStartsFrom
Indicates that a standard or predefined route has its starting point at a specified location or entity.
-
B.
standardRouteClass
Indicates that a route is classified according to a predefined standard category or class used for routing or transportation.
-
C.
standardNumber
Indicates that an entity is associated with a canonical or officially recognized reference number used for identification or classification.
-
D.
standardRouteProtection
Indicates that a route or path is safeguarded according to a predefined, typical set of security or safety measures.
-
E.
stationingBasis
Indicates the underlying reason, justification, or criteria for assigning or positioning an entity at a particular location or post.
- F. None of above. chosen
Provenance (4 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e2025888190a2b6240296bba13e |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:10 a.m.