Triple
T33138161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lasqueti Island |
E848067
|
entity |
| Predicate | hasRoadConnectionToMainland |
P19137
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Lasqueti Island, hasRoadConnectionToMainland, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoadConnectionToMainland Context triple: [Lasqueti Island, hasRoadConnectionToMainland, false]
-
A.
connectedToMainlandBy
chosen
Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
-
B.
hasAccessToMainland
Indicates that an entity is able or permitted to reach, enter, or use the mainland from another location.
-
C.
hasBridgeOrFerryConnection
Indicates that there exists a bridge or ferry link enabling direct passage or transport between the related entities.
-
D.
connectsMainland
Indicates a relationship where something serves as a link or route joining a mainland to another land area or location.
-
E.
hasApproximateTravelTimeToMainland
Indicates that one location is associated with an estimated or approximate amount of time required to travel from it to the mainland.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: May 1, 2026, 1:27 a.m.