Triple
T25196620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pointe Whymper |
E631016
|
entity |
| Predicate | situatedInSubrange |
P52888
|
FINISHED |
| Object | Graian Alps |
—
|
NE NERFINISHED |
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: Graian Alps | Statement: [Pointe Whymper, situatedInSubrange, Graian Alps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedInSubrange Context triple: [Pointe Whymper, situatedInSubrange, Graian Alps]
-
A.
climbedInSubrange
Indicates that one entity’s climbing action occurred within a specified subrange of another entity’s climb or of a defined interval.
-
B.
locatedBetween
Indicates that one entity is positioned spatially between two other reference entities.
-
C.
partOfRange
chosen
Indicates that one entity is included within, or constitutes a segment of, the overall extent or span defined by another entity.
-
D.
isInSubregion
Indicates that one region or area is located within the boundaries of another, more specific subregion.
-
E.
subrange
Indicates that one value or interval lies entirely within the bounds of another value or interval.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46e143e908190a3dff0f3a2399970 |
completed | May 1, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:50 p.m.