Triple
T15137644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keramoti |
E361595
|
entity |
| Predicate | distanceToThasosByFerry |
P117466
|
FINISHED |
| Object | short crossing |
—
|
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: short crossing | Statement: [Keramoti, distanceToThasosByFerry, short crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToThasosByFerry Context triple: [Keramoti, distanceToThasosByFerry, short crossing]
-
A.
distanceToPiraeus
Indicates the spatial distance between a given location or object and Piraeus.
-
B.
distanceFromAthensBySea
Indicates the measured distance between a place and Athens when traveling via sea routes.
-
C.
distanceToThessaloniki
Indicates the spatial distance between a given entity’s location and the city of Thessaloniki.
-
D.
approxDistanceToMytilene
Indicates that one entity is located at an approximate distance from the place or reference point named Mytilene.
-
E.
distanceToLesbos
Indicates the spatial distance between a given entity and the location of Lesbos.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b59b488190b0016970647e7483 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:07 a.m.