Triple
T14399261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Bertilak |
E357026
|
entity |
| Predicate | goalOfPlot |
P42284
|
FINISHED |
| Object | to frighten Guinevere |
—
|
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 frighten Guinevere | Statement: [Lord Bertilak, goalOfPlot, to frighten Guinevere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfPlot Context triple: [Lord Bertilak, goalOfPlot, to frighten Guinevere]
-
A.
narrativeGoal
chosen
Indicates that one entity has a desired outcome or objective within a story or narrative context that drives their actions or development.
-
B.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
C.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
E.
aimOf
Indicates that one entity serves as the goal, purpose, or intended target of another entity’s action, plan, or existence.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9083f9d081908fe5c99655c410b3 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.