Triple
T24122910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Far de la Mola |
E597711
|
entity |
| Predicate | hasElevationRelativeToSea |
P114161
|
FINISHED |
| Object | clifftop position |
—
|
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: clifftop position | Statement: [Far de la Mola, hasElevationRelativeToSea, clifftop position]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElevationRelativeToSea Context triple: [Far de la Mola, hasElevationRelativeToSea, clifftop position]
-
A.
hasElevationRelativeToSeaLevel
chosen
Indicates the elevation or height of an entity measured relative to mean sea level.
-
B.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
C.
hasTypicalElevationRelativeTo
Indicates the usual height or altitude of one entity in comparison to a referenced baseline or other entity.
-
D.
elevationAboveSeaLevelUnit
Indicates the unit of measurement used to express an entity’s elevation above sea level.
-
E.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee5937c819092396751c23553ca |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:06 p.m.