Triple
T20865342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John-Boy Walton |
E513745
|
entity |
| Predicate | creativeWorkGoal |
P114985
|
FINISHED |
| Object | to become a novelist |
—
|
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: to become a novelist | Statement: [John-Boy Walton, creativeWorkGoal, to become a novelist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeWorkGoal Context triple: [John-Boy Walton, creativeWorkGoal, to become a novelist]
-
A.
creativeWorkFocus
Indicates that one entity is the primary subject, theme, or focal point of another entity’s creative work.
-
B.
creativeWorkOn
Indicates a relationship where an entity has created, contributed to, or worked on a particular creative work (such as a book, artwork, film, or other intellectual product).
-
C.
narrativeGoal
Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
-
D.
hasCreativeGoal
chosen
Indicates that an entity possesses or is pursuing a specific creative objective or intended creative outcome.
-
E.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
- 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_69e0b4f675cc8190b4e745225b62eb66 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c45fbfc88190914c5133aa4b242c |
completed | April 21, 2026, 12:27 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.