Triple
T17047874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Çeşme |
E413615
|
entity |
| Predicate | ferryConnections |
P1831
|
FINISHED |
| Object | Chios Island |
—
|
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: Chios Island | Statement: [Çeşme, ferryConnections, Chios Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ferryConnections Context triple: [Çeşme, ferryConnections, Chios Island]
-
A.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
B.
hasBridgeOrFerryConnection
Indicates that there exists a bridge or ferry link enabling direct passage or transport between the related entities.
-
C.
linkedByFerryTo
chosen
Indicates that one place is connected to another by a ferry route that enables transport between them.
-
D.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
E.
hasNearbyFerryRoute
Indicates that there is a ferry route located close to the referenced 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9f799c8190a683ae38cd990643 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.