Triple
T23303083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Ravine |
E590357
|
entity |
| Predicate | accessTrailheadNear |
P30481
|
FINISHED |
| Object | Appalachia trailhead on U.S. Route 2 |
—
|
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: Appalachia trailhead on U.S. Route 2 | Statement: [King Ravine, accessTrailheadNear, Appalachia trailhead on U.S. Route 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessTrailheadNear Context triple: [King Ravine, accessTrailheadNear, Appalachia trailhead on U.S. Route 2]
-
A.
accessTrailhead
chosen
Indicates that an entity has a way to reach or enter a specific trailhead location.
-
B.
accessTrailheadArea
Indicates that an entity is permitted to enter or use a designated trailhead area.
-
C.
alternativeTrailhead
Indicates that one trailhead serves as an alternative starting point or access location for the same trail as another trailhead.
-
D.
standardTrailhead
Indicates that a location serves as a designated, officially recognized starting point for a trail.
-
E.
trailheadType
Indicates the specific kind or classification of a trailhead associated with a trail or route.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972406a08190bbf355cc7a9f8432 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.