Triple
T14144950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alps four-thousanders |
E350521
|
entity |
| Predicate | hasHighestMemberElevation |
P46534
|
FINISHED |
| Object | 4808 metres |
—
|
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: 4808 metres | Statement: [Alps four-thousanders, hasHighestMemberElevation, 4808 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestMemberElevation Context triple: [Alps four-thousanders, hasHighestMemberElevation, 4808 metres]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
highestElevationApprox
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
C.
hasAverageElevation
Indicates that an entity is characterized by a specific mean height above a defined reference level, typically sea level.
-
D.
hasTopElevation
chosen
Indicates that an entity has a specified maximum or highest elevation value.
-
E.
highestPassApproxElevation
Indicates the approximate elevation of the highest pass along a given route or within a specified area.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61214de081909a5186ff11336f97 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:53 a.m.