Triple
T38377252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogashima cliffs |
E893657
|
entity |
| Predicate | hasBoatTourDeparturePoint |
P189343
|
FINISHED |
| Object | Dogashima port |
—
|
NE NERFINISHED |
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: Dogashima port | Statement: [Dogashima cliffs, hasBoatTourDeparturePoint, Dogashima port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBoatTourDeparturePoint Context triple: [Dogashima cliffs, hasBoatTourDeparturePoint, Dogashima port]
-
A.
hasBoatDeparturePoint
chosen
Indicates the location from which a boat departs.
-
B.
hasCruiseDeparturePoint
Indicates the location from which a cruise journey is scheduled to start or depart.
-
C.
isBoatingLandmark
Indicates that a location serves as a notable reference point or feature specifically used for boating navigation or activities.
-
D.
hasBoatFacility
Indicates that an entity provides or is equipped with facilities or services specifically for boats.
-
E.
hasBoatRides
Indicates that one entity offers, provides, or features boat rides in relation to another entity.
- 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_69f76e4b1f748190a380696a16eae4a2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:31 p.m.