Triple
T27230918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nephin |
E682151
|
entity |
| Predicate | summitTerrain |
P162267
|
FINISHED |
| Object | stony and exposed |
—
|
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: stony and exposed | Statement: [Nephin, summitTerrain, stony and exposed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitTerrain Context triple: [Nephin, summitTerrain, stony and exposed]
-
A.
summitDifficulty
Indicates the level of challenge or effort required to reach the summit of something (typically a mountain or peak).
-
B.
summitRefuge
Indicates a refuge, shelter, or hut that is located on or very near a mountain summit and serves as a protective or resting place for summit visitors.
-
C.
summitAboveTreeline
Indicates that the summit of a landform is located above the natural treeline, where trees no longer grow due to environmental conditions.
-
D.
summitRockType
Indicates the type of rock that composes or characterizes the summit of a geographic feature.
-
E.
summitShape
Indicates the geometric form or contour that characterizes the topmost point or summit of an object or landform.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264ec31081908b14cbdbc604d437 |
completed | May 2, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:46 a.m.