Triple
T21290115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavdos |
E524762
|
entity |
| Predicate | extremePointType |
P47428
|
FINISHED |
| Object | southernmost point |
—
|
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: southernmost point | Statement: [Gavdos, extremePointType, southernmost point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extremePointType Context triple: [Gavdos, extremePointType, southernmost point]
-
A.
hasExtremePoint
Indicates that one entity possesses or includes another entity that is an extreme (e.g., maximum or minimum) point within its structure or boundary.
-
B.
directionalExtreme
chosen
Indicates that one entity lies at or near the furthest extent or boundary in a specified direction relative to another entity.
-
C.
peakType
Indicates the specific classification or category of a peak based on its form, prominence, or other defining characteristics.
-
D.
apexOf
Indicates that one entity is the highest or most extreme point, level, or culmination of another entity or process.
-
E.
criticalPoints
Indicates that certain points in a domain are locations where a function’s derivative (or gradient) is zero or undefined, marking potential local maxima, minima, or saddle points.
- 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_69e0b5171f6c8190a5d57201ede73811 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736d9467881908ec5b1dec76e6f5d |
completed | April 21, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:03 p.m.