Triple
T19172798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croz Spur |
E469366
|
entity |
| Predicate | onMountainFace |
P73665
|
FINISHED |
| Object | north face |
—
|
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: north face | Statement: [Croz Spur, onMountainFace, north face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onMountainFace Context triple: [Croz Spur, onMountainFace, north face]
-
A.
sideOfMountain
chosen
Indicates that one entity is located on or corresponds to a particular side or face of a mountain relative to another entity.
-
B.
operatesOnMountain
Indicates that an entity performs operations, activities, or functions on or in relation to a mountain.
-
C.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
-
D.
endPointMountain
Indicates that a path, route, or boundary terminates at a mountain.
-
E.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16544948190bd10ca7804dd27a5 |
completed | April 20, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.