Triple
T37397147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chunnambar Boat House |
E928884
|
entity |
| Predicate | boardingPointFor |
P118590
|
FINISHED |
| Object | boat rides to Paradise Beach |
—
|
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: boat rides to Paradise Beach | Statement: [Chunnambar Boat House, boardingPointFor, boat rides to Paradise Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boardingPointFor Context triple: [Chunnambar Boat House, boardingPointFor, boat rides to Paradise Beach]
-
A.
boardingFor
chosen
Indicates that one entity serves as the designated boarding location or facility for another entity, such as passengers or animals.
-
B.
boardingPlatform
Indicates the platform or area where a passenger boards a vehicle or form of transport.
-
C.
landingPlace
Indicates the location or surface where something or someone comes down to rest after moving through the air or space.
-
D.
transportTerminusFor
Indicates that a location serves as the endpoint or final stop for a particular transport route or service.
-
E.
isMainArrivalPointFor
Indicates that a location serves as the primary arrival point for a given entity or flow of entities.
- 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:16 p.m.