Triple
T4565115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko’okiri Body Plunge |
E121889
|
entity |
| Predicate | usesRideVehicle |
P12443
|
FINISHED |
| Object | rider’s body |
—
|
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: rider’s body | Statement: [Ko’okiri Body Plunge, usesRideVehicle, rider’s body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRideVehicle Context triple: [Ko’okiri Body Plunge, usesRideVehicle, rider’s body]
-
A.
hasRideCycle
Indicates that one entity is associated with, or participates in, a recurring sequence or cycle of rides or ride operations.
-
B.
vehicleUsed
chosen
Indicates that a particular vehicle is utilized or employed in performing an action, event, or activity.
-
C.
canRideBy
Indicates that one entity is able to travel or move by means of another entity (such as a vehicle, animal, or transport mode).
-
D.
hasPrimaryVehicularAccessTo
Indicates that one location or entity serves as the main route or means by which vehicles can reach or enter another location or entity.
-
E.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd589cde9081909b84186d700fc463 |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.