Triple
T29865214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston–Wolfe Island ferry route |
E758435
|
entity |
| Predicate | hasIslandTerminus |
P170747
|
FINISHED |
| Object | Wolfe 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: Wolfe Island | Statement: [Kingston–Wolfe Island ferry route, hasIslandTerminus, Wolfe Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIslandTerminus Context triple: [Kingston–Wolfe Island ferry route, hasIslandTerminus, Wolfe Island]
-
A.
hasIsland
Indicates that one entity possesses, contains, or includes an island as part of its domain, territory, or structure.
-
B.
hasIslandConnection
Indicates that there exists a connection or link between entities that specifically involves or passes through an island.
-
C.
hasIslandLanding
Indicates that an entity includes or provides a designated landing area or facility located on an island.
-
D.
hasIslandPlatforms
Indicates that the subject has one or more island-style platforms, typically positioned between tracks and accessible from both sides.
-
E.
meetsInIsland
Indicates that two or more entities meet with each other at a location that is an island.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 5:51 p.m.