Triple
T2894810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trail Crest |
E63910
|
entity |
| Predicate | onSideOf |
P31095
|
FINISHED |
| Object | eastern slope of the Sierra Nevada |
—
|
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: eastern slope of the Sierra Nevada | Statement: [Trail Crest, onSideOf, eastern slope of the Sierra Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onSideOf Context triple: [Trail Crest, onSideOf, eastern slope of the Sierra Nevada]
-
A.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
B.
A-sideOf
Indicates that one entity is located on or corresponds to the A-side (first or primary side) of another entity, typically in a two-sided context.
-
C.
nearSideDominatedBy
Indicates that the near side of an object or region is primarily influenced, controlled, or characterized by another specified entity or factor.
-
D.
liesOnFlankOf
Indicates that one entity is positioned along the side or lateral edge of another entity.
-
E.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe06509808190b673222b9ae3d599 |
completed | March 7, 2026, 8:23 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:07 p.m.