Triple
T24699620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomerang Coast to Coaster |
E611694
|
entity |
| Predicate | rideDirection |
P129985
|
FINISHED |
| Object | forward and backward |
—
|
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: forward and backward | Statement: [Boomerang Coast to Coaster, rideDirection, forward and backward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rideDirection Context triple: [Boomerang Coast to Coaster, rideDirection, forward and backward]
-
A.
transportDirection
Indicates the directional flow or route along which something is transported from an origin toward a destination.
-
B.
directionType
chosen
Indicates the specific kind or category of direction associated with a movement, orientation, or relation between entities.
-
C.
departureDirection
Indicates the direction or bearing in which an entity moves away from its point of origin or starting location.
-
D.
routeDirectionB
Indicates that one entity represents the direction or orientation of a route or path relative to another entity.
-
E.
routeDirectionA
Indicates the primary or first directional orientation or heading associated with a specific route.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:22 a.m.