Triple
T29486763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nye Mountain |
E747944
|
entity |
| Predicate | hasOfficialTrail |
P175254
|
FINISHED |
| Object | no official maintained trail to summit |
—
|
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: no official maintained trail to summit | Statement: [Nye Mountain, hasOfficialTrail, no official maintained trail to summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialTrail Context triple: [Nye Mountain, hasOfficialTrail, no official maintained trail to summit]
-
A.
hasOfficialTrailhead
Indicates that a location or route is associated with a formally designated and recognized starting point for a trail.
-
B.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
C.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
D.
isOfficialTrailToSummit
Indicates that a trail is an officially designated and recognized route leading to the summit.
-
E.
hasTrailFeature
Indicates that a trail possesses or is characterized by a specific feature or attribute.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 4:09 p.m.