Triple
T18662849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billie the oiler |
E456244
|
entity |
| Predicate | sceneInvolvedIn |
P107448
|
FINISHED |
| Object | rowing the boat through rough seas |
—
|
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: rowing the boat through rough seas | Statement: [Billie the oiler, sceneInvolvedIn, rowing the boat through rough seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sceneInvolvedIn Context triple: [Billie the oiler, sceneInvolvedIn, rowing the boat through rough seas]
-
A.
scenes
chosen
Indicates that one entity is a scene or setting in which the other entity occurs, appears, or is depicted.
-
B.
hasBeenInvolvedIn
Indicates that an entity has participated in, taken part in, or been connected to a particular event, activity, or situation.
-
C.
questInvolvedIn
Indicates that an entity participates in, is associated with, or plays a role in a particular quest or mission.
-
D.
relativeInvolvedInEvent
Indicates that a person’s relative participates in, is affected by, or is otherwise involved in a particular event.
-
E.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5508c0d088190bef46fb3a3001f10 |
completed | April 19, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.