Triple
T22773707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Rotondo |
E563632
|
entity |
| Predicate | rankingByElevationInCorsica |
P149675
|
FINISHED |
| Object | second highest peak in Corsica |
—
|
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: second highest peak in Corsica | Statement: [Monte Rotondo, rankingByElevationInCorsica, second highest peak in Corsica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingByElevationInCorsica Context triple: [Monte Rotondo, rankingByElevationInCorsica, second highest peak in Corsica]
-
A.
rankingInFranceByHeight
Indicates the relative order of entities in France based on their height, from tallest to shortest or vice versa.
-
B.
rankingByLengthInAlps
Indicates an ordering of entities based on their relative lengths specifically within the context of the Alps.
-
C.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
-
D.
regionRankByHeight
Indicates the relative ordering of regions based on their height or elevation.
-
E.
highestCampAltitudeMetres
Indicates the maximum altitude in meters reached by any camp associated with the entity.
- F. None of above. chosen
Provenance (4 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b6040048190a36fa759e06136ea |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:27 p.m.