Triple
T33554546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poros town |
E859436
|
entity |
| Predicate | approxTravelTimeFromAthensByFerry |
P70601
|
FINISHED |
| Object | about 1–2 hours |
—
|
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: about 1–2 hours | Statement: [Poros town, approxTravelTimeFromAthensByFerry, about 1–2 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxTravelTimeFromAthensByFerry Context triple: [Poros town, approxTravelTimeFromAthensByFerry, about 1–2 hours]
-
A.
distanceFromAthensBySea
Indicates the measured distance between a place and Athens when traveling via sea routes.
-
B.
distanceToThasosByFerry
Indicates the measured distance required to travel to Thasos specifically by ferry route.
-
C.
distanceToPiraeus
Indicates the spatial distance between a given location or object and Piraeus.
-
D.
travelTimeByFerry
chosen
Indicates the duration required to travel between two locations specifically using a ferry as the mode of transportation.
-
E.
distanceFromAthensAirport
Indicates the spatial distance between a given location and Athens Airport.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 1, 2026, 1:40 a.m.