Triple

T37614550
Position Surface form Disambiguated ID Type / Status
Subject Lipayran Island E935881 entity
Predicate hasAccessToMainland P193230 FINISHED
Object by boat 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: by boat | Statement: [Lipayran Island, hasAccessToMainland, by boat]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAccessToMainland
Context triple: [Lipayran Island, hasAccessToMainland, by boat]
  • A. isRemoteFromMainland
    Indicates that a location is geographically separated and distant from the primary mainland area of a region or country.
  • B. appliesToMainland
    Indicates that something is relevant or applicable specifically to the mainland portion of a territory, excluding its islands or overseas areas.
  • C. hasApproximateTravelTimeToMainland
    Indicates that one location is associated with an estimated or approximate amount of time required to travel from it to the mainland.
  • D. connectedToMainlandBy
    Indicates that one landmass or area is physically linked to a mainland, typically via a bridge, causeway, or other continuous connection.
  • E. terminalOnMainland
    Indicates that a transportation or service terminal is physically located on the mainland rather than on an island or offshore location.
  • 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_69f76ed16b748190ad6add183b1be688 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fd3a69f1e08190a11aed015bff0858 completed May 8, 2026, 1:20 a.m.
PD Predicate disambiguation batch_69fd39124180819080ca7911d3515d6d completed May 8, 2026, 1:14 a.m.
PDg Predicate description generation batch_69fd3a6905b88190ae12b43576f4cc63 completed May 8, 2026, 1:20 a.m.
Created at: May 3, 2026, 4:18 p.m.