Triple
T30211157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Μαίναλο |
E768069
|
entity |
| Predicate | βρίσκεται_στην_περιφέρεια |
P46039
|
FINISHED |
| Object | Πελοπόννησος |
—
|
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: Πελοπόννησος | Statement: [Μαίναλο, βρίσκεται_στην_περιφέρεια, Πελοπόννησος]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: βρίσκεται_στην_περιφέρεια Context triple: [Μαίναλο, βρίσκεται_στην_περιφέρεια, Πελοπόννησος]
-
A.
isLocatedBetweenMajorRegionsOfGreece
Indicates that something is geographically situated in an area lying between two or more major regions 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.
δραστηριοποιείταιΣε
Indicates that an entity is active, operates, or conducts its activities within a specified area, field, or context.
-
D.
periphery
chosen
Indicates a relationship where one entity is located at, or associated with, the outer edge or boundary region of another entity.
-
E.
crossesAdministrativeRegionOfGreece
Indicates that one entity passes through or extends across the administrative region of Greece associated with another entity.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff185488190a49b208e4ac6cf59 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:32 p.m.