Triple
T8231421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico Turquino |
E192300
|
entity |
| Predicate | summitCoordinates |
P7610
|
FINISHED |
| Object | approximate latitude 19.99°N |
—
|
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: approximate latitude 19.99°N | Statement: [Pico Turquino, summitCoordinates, approximate latitude 19.99°N]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitCoordinates Context triple: [Pico Turquino, summitCoordinates, approximate latitude 19.99°N]
-
A.
hasSummitCoordinates
chosen
Indicates that an entity has specific geographic coordinates identifying the location of its summit.
-
B.
summitLocatedIn
Indicates that a summit (mountain peak) is geographically situated within a specified area or region.
-
C.
hasSummitLongitude
Indicates the longitudinal coordinate at which the summit or highest point of an entity is located.
-
D.
summitLocatedBetween
Indicates that a summit is situated geographically between two other specified locations or landmarks.
-
E.
summitElevation
Indicates the elevation or height of a summit above a reference level, typically sea level.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7824a6c48190a3abb76c4c3dcc71 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:46 p.m.