Triple
T13700161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Utah |
E328493
|
entity |
| Predicate | letsGo |
P111222
|
FINISHED |
| Object | allows Bodhi to surf the final wave |
—
|
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: allows Bodhi to surf the final wave | Statement: [Johnny Utah, letsGo, allows Bodhi to surf the final wave]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: letsGo Context triple: [Johnny Utah, letsGo, allows Bodhi to surf the final wave]
-
A.
goesTo
Indicates that one entity moves or travels from its current location to another specified location or entity.
-
B.
launchesTo
Indicates that one entity initiates the sending or propulsion of another entity toward a specific destination or into a particular trajectory.
-
C.
wentTo
Indicates that one entity traveled or moved from its original location to another specified place.
-
D.
wentTheDistance
Indicates that an entity persisted through an entire challenge, task, or event without giving up or stopping early.
-
E.
goesOn
Indicates that one entity participates in, boards, or travels using another entity, such as a vehicle, trip, or event.
- F. None of above. chosen
Provenance (4 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc879adc88190b03f1cf815b71061 |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:54 p.m.