Triple
T26362047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catseye Beach |
E660232
|
entity |
| Predicate | hasTransportOptionNearby |
P6208
|
FINISHED |
| Object | island shuttle buses |
—
|
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: island shuttle buses | Statement: [Catseye Beach, hasTransportOptionNearby, island shuttle buses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportOptionNearby Context triple: [Catseye Beach, hasTransportOptionNearby, island shuttle buses]
-
A.
hasTransportationProximityTo
Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
-
B.
hasNearbyTransportationCorridor
Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
-
C.
transportationNearby
chosen
Indicates that there is a transportation facility or service located close to the referenced entity.
-
D.
operatorOfNearbyTransit
Indicates that an entity operates or manages a public transit service located in close geographic proximity to another specified entity.
-
E.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
- 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_69ee8126d52c8190bc0b34337c2c9aa8 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 26, 2026, 10:52 p.m.