Triple
T25336071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub Dome |
E635281
|
entity |
| Predicate | trailFeatureType |
P158457
|
FINISHED |
| Object | steep rocky shoulder |
—
|
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: steep rocky shoulder | Statement: [Sub Dome, trailFeatureType, steep rocky shoulder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailFeatureType Context triple: [Sub Dome, trailFeatureType, steep rocky shoulder]
-
A.
trailDesignation
Indicates that a particular label, name, or classification has been assigned to a trail to identify its route, type, or official status.
-
B.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
C.
trailUses
Indicates that a trail supports or is designated for specific types of use or activities (such as hiking, biking, or horseback riding).
-
D.
roadFeature
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
-
E.
trailAccess
Indicates that one entity provides permission or a route for another entity to enter, use, or traverse a specific trail or pathway.
- 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_69e75a99bd6481909476115b35b9a8e4 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497ca0f18819090168e3221c2aa32 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:32 p.m.