Triple
T38461202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Carrigain |
E912456
|
entity |
| Predicate | trailLengthPrimaryRoute |
P68820
|
FINISHED |
| Object | approximately 10 mi round trip via Signal Ridge Trail |
—
|
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 10 mi round trip via Signal Ridge Trail | Statement: [Mount Carrigain, trailLengthPrimaryRoute, approximately 10 mi round trip via Signal Ridge Trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailLengthPrimaryRoute Context triple: [Mount Carrigain, trailLengthPrimaryRoute, approximately 10 mi round trip via Signal Ridge Trail]
-
A.
mainStraightLengthKm
Indicates the length, measured in kilometers, of the primary straight segment associated with the entity.
-
B.
roadLength
Indicates the measured distance or extent of a road, typically expressed in units of length.
-
C.
trailSystemLength
Indicates the total measured length of a trail system associated with an entity.
-
D.
trailTypeToReach
Indicates the type or kind of trail or path that must be used to reach a particular location or destination.
-
E.
totalRouteLength
chosen
Indicates the overall distance or length of an entire route when all its segments are combined.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.