Triple
T5100666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cannonball (LIRR train) |
E114972
|
entity |
| Predicate | destinationType |
P30653
|
FINISHED |
| Object | beach destinations |
—
|
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: beach destinations | Statement: [Cannonball (LIRR train), destinationType, beach destinations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationType Context triple: [Cannonball (LIRR train), destinationType, beach destinations]
-
A.
servesDestinationType
chosen
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
B.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
-
C.
arrivalLocationType
Indicates the type or category of place where an arrival occurs in the described relationship or event.
-
D.
voyageType
Indicates the specific category or nature of a journey or trip that an entity undertakes.
-
E.
transportGoal
Indicates that an entity has the objective or intended outcome of moving or conveying something or someone from one place 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd758381dc8190ac491788d27ab8e0 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.