Triple
T21300913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neochori Mesolongiou |
E525058
|
entity |
| Predicate | distanceToMissolonghi |
P143649
|
FINISHED |
| Object | approximately 5 km |
—
|
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: approximately 5 km | Statement: [Neochori Mesolongiou, distanceToMissolonghi, approximately 5 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMissolonghi Context triple: [Neochori Mesolongiou, distanceToMissolonghi, approximately 5 km]
-
A.
distanceToThessaloniki
Indicates the spatial distance between a given entity’s location and the city of Thessaloniki.
-
B.
approxDistanceToMytilene
Indicates that one entity is located at an approximate distance from the place or reference point named Mytilene.
-
C.
distanceToVolos
Indicates the spatial distance between a given entity and the location of Volos.
-
D.
distanceToIalysos
Indicates a spatial relationship specifying the distance between a given entity and the location Ialysos.
-
E.
distanceFromThessaloniki
Indicates the spatial distance between a given entity and the city of Thessaloniki.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385c078881908a451be1a19a64c5 |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e6190163448190a2404b396215c686 |
completed | April 20, 2026, 12:16 p.m. |
Created at: April 16, 2026, 4:05 p.m.