Triple
T18468298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Storm King |
E451222
|
entity |
| Predicate | hasTrailCharacteristic |
P75080
|
FINISHED |
| Object | significant elevation gain |
—
|
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: significant elevation gain | Statement: [Mount Storm King, hasTrailCharacteristic, significant elevation gain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrailCharacteristic Context triple: [Mount Storm King, hasTrailCharacteristic, significant elevation gain]
-
A.
hasTrailFeature
chosen
Indicates that a trail possesses or is characterized by a specific feature or attribute.
-
B.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
C.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
-
D.
hasTrailConnection
Indicates that one location is connected to another by a traversable trail or path.
-
E.
hasTrailStatus
Indicates the current condition or accessibility state assigned to a trail.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a857b1481908ebfcf832c83376f |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.