Triple
T24434519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaputian Beach |
E616087
|
entity |
| Predicate | isAccessMethod |
P56178
|
FINISHED |
| Object | ferry to Samal Island |
—
|
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 to Samal Island | Statement: [Kaputian Beach, isAccessMethod, ferry to Samal Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessMethod Context triple: [Kaputian Beach, isAccessMethod, ferry to Samal Island]
-
A.
hasAccessMethod
chosen
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
B.
accessMethod
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
C.
usesAccessMethod
Indicates that one entity employs or relies on a particular access method to reach, interact with, or retrieve another entity or resource.
-
D.
isPartOfAccessSystem
Indicates that something functions as a component or element within a larger access control or access management system.
-
E.
isTerminusAccessFor
Indicates that one location or facility serves as an access point or terminal endpoint for another transportation route, service, or system.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297855fd08190904eedd2666d9622 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:16 a.m.