Triple
T21771246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flega |
E537433
|
entity |
| Predicate | relativeElevationInGreece |
P145896
|
FINISHED |
| Object | one of the highest peaks in Greece |
—
|
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: one of the highest peaks in Greece | Statement: [Flega, relativeElevationInGreece, one of the highest peaks in Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeElevationInGreece Context triple: [Flega, relativeElevationInGreece, one of the highest peaks in Greece]
-
A.
rankByAreaInGreece
Indicates the relative ordering of entities based on their area size within the geographic boundaries of Greece.
-
B.
locatedOnSideOfGreekMainland
Indicates that one place is situated on the side of the Greek mainland relative to another reference point or area.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
elevation
Indicates the vertical height or altitude of one entity relative to a reference level or another entity.
-
E.
hasElevationRelativeToSeaLevel
Indicates the elevation or height of an entity measured relative to mean sea level.
- F. None of above. chosen
Provenance (4 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_69e0c470759c819094a215757113562b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031aea8c88190b4bc57df6f269ba6 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.