Triple
T6037100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corsican Mountains |
E134448
|
entity |
| Predicate | highestElevationsReach |
P19320
|
FINISHED |
| Object | over 2700 m |
—
|
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: over 2700 m | Statement: [Corsican Mountains, highestElevationsReach, over 2700 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestElevationsReach Context triple: [Corsican Mountains, highestElevationsReach, over 2700 m]
-
A.
highestElevationApprox
chosen
Indicates that an entity has an approximate value for the maximum elevation reached within its spatial or conceptual extent.
-
B.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
C.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
-
D.
highestRoadPassIn
Indicates that a location contains the highest-elevation road pass within a specified area or region.
-
E.
pilgrimageAltitudeHighPoint
Indicates the highest altitude reached along a pilgrimage route or during a pilgrimage journey.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056cb06508190a90beb4d9d083835 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.