Triple
T17723920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethany Hamilton |
E442410
|
entity |
| Predicate | resumedSurfing |
P44197
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bethany Hamilton, resumedSurfing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumedSurfing Context triple: [Bethany Hamilton, resumedSurfing, yes]
-
A.
learnsToSurfFrom
Indicates that one entity acquires or practices surfing skills under the instruction, guidance, or example of another entity.
-
B.
resumedIn
chosen
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
C.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
D.
surfingLevelRequired
Indicates the minimum surfing skill or proficiency level that an entity must have in order to participate in or access another entity or activity.
-
E.
resumesAfter
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4748900608190bf5ba04415edaffc |
completed | April 19, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:07 a.m.