Triple
T2727724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Perdido |
E60232
|
entity |
| Predicate | rankingInPyreneesByElevation |
P39147
|
FINISHED |
| Object | third-highest peak in the Pyrenees |
—
|
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: third-highest peak in the Pyrenees | Statement: [Monte Perdido, rankingInPyreneesByElevation, third-highest peak in the Pyrenees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingInPyreneesByElevation Context triple: [Monte Perdido, rankingInPyreneesByElevation, third-highest peak in the Pyrenees]
-
A.
summitElevationRank
chosen
Indicates the relative position of a summit in an ordered list based on its elevation compared to other summits.
-
B.
distanceToPyrenees
Indicates the spatial distance between a given location or entity and the Pyrenees.
-
C.
territorialPeak
Indicates the highest geographical point located within the territory or jurisdiction of a given entity.
-
D.
notablePeak
Indicates that one entity is a peak or summit that is especially prominent, famous, or significant in relation to another entity.
-
E.
areaPeak
Indicates that a specified location or region is the highest point (peak) within a given area or spatial extent.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdacffa6481909df37335e8fdd595 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.