Triple
T35577311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Holes dive site |
E1028114
|
entity |
| Predicate | bestAccessedFrom |
P116227
|
FINISHED |
| Object | day boats from Koror |
—
|
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: day boats from Koror | Statement: [Blue Holes dive site, bestAccessedFrom, day boats from Koror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestAccessedFrom Context triple: [Blue Holes dive site, bestAccessedFrom, day boats from Koror]
-
A.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
B.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
bestVisitedAs
Indicates that one entity is most suitably or optimally experienced when visited in the context or manner specified by another entity.
-
D.
bestVisitedBy
Indicates that an entity is most suitably or optimally accessed, experienced, or reached by using a particular mode, route, or means of visiting.
-
E.
bestAccessPoint
chosen
Indicates that one access point is considered the most suitable or optimal choice for connecting to a given entity or location among available alternatives.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.