Triple
T19099975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Siesta |
E467505
|
entity |
| Predicate | mountainFace |
P73665
|
FINISHED |
| Object | north face of the Grandes Jorasses |
—
|
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 of the Grandes Jorasses | Statement: [No Siesta, mountainFace, north face of the Grandes Jorasses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainFace Context triple: [No Siesta, mountainFace, north face of the Grandes Jorasses]
-
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.
mountainFeature
Indicates that one entity is a notable physical or geographical feature associated with, located on, or forming part of a mountain.
-
C.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
D.
sourceMountain
Indicates that something originates from, or has its source in, a particular mountain.
-
E.
mountainType
Indicates the specific classification or category of a mountain based on its geological or physical characteristics.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e36d279081908aeb472cd740c302 |
completed | April 20, 2026, 8:27 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:04 p.m.