Triple
T31784513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Massif |
E811291
|
entity |
| Predicate | highestMassifOf |
P157832
|
FINISHED |
| Object | Picos de Europa |
—
|
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: Picos de Europa | Statement: [Central Massif, highestMassifOf, Picos de Europa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestMassifOf Context triple: [Central Massif, highestMassifOf, Picos de Europa]
-
A.
highestMassifAmong
chosen
Indicates that one massif has the greatest height or prominence among a specified set of massifs.
-
B.
nearestMountainMassif
Indicates that one mountain massif is the closest in distance to a given reference location or entity compared to all other mountain massifs.
-
C.
isPartOfHighestMassifOf
Indicates that one entity is a constituent part or subfeature of the highest massif within a given geographic or topographic context.
-
D.
nearHighestPeakOf
Indicates that one entity is located close to the highest peak of another referenced geographic or topographic feature.
-
E.
prominenceOfHighestPeak_m
Indicates the vertical prominence, in meters, of the highest peak relative to the lowest contour line encircling it and no higher summit.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 30, 2026, 11:37 p.m.