Triple
T14279683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trizina |
E354009
|
entity |
| Predicate | hasNearbyIslandConnection |
P65644
|
FINISHED |
| Object | Ferry connection Galatas–Poros |
—
|
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: Ferry connection Galatas–Poros | Statement: [Trizina, hasNearbyIslandConnection, Ferry connection Galatas–Poros]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyIslandConnection Context triple: [Trizina, hasNearbyIslandConnection, Ferry connection Galatas–Poros]
-
A.
nearbyIslandConnection
chosen
Indicates a connection or link between islands that are geographically close to each other.
-
B.
hasIslandNearby
Indicates that one location is situated close to an island in geographic space.
-
C.
neighboringIsland
Indicates that one island is geographically adjacent to or very close to another island, typically separated only by a narrow body of water.
-
D.
hasIsland
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
-
E.
nearIsland
Indicates that one entity is located close to or in the vicinity of an island.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6585270c8190a717127b2f5dab3b |
completed | April 14, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.