Triple
T31838857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Wilson |
E812745
|
entity |
| Predicate | commonPlotFunction |
P88311
|
FINISHED |
| Object | source of conflict and comedy |
—
|
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: source of conflict and comedy | Statement: [George Wilson, commonPlotFunction, source of conflict and comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPlotFunction Context triple: [George Wilson, commonPlotFunction, source of conflict and comedy]
-
A.
commonPlotUse
Indicates that a particular plot element, device, or storyline is frequently employed or reused across multiple works or narratives.
-
B.
coPlotter
Indicates that two or more entities jointly create, develop, or contribute to the plot of a narrative work.
-
C.
primaryFunctionInPlot
chosen
Indicates the main narrative role or purpose that an entity serves within the plot of a story.
-
D.
hasCommonPlotElement
Indicates that two narrative works share at least one similar or overlapping plot component, event, or storyline feature.
-
E.
plotElement
Indicates that one entity functions as a narrative component or structural element within the storyline of another entity (such as a work of fiction or media).
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 30, 2026, 11:48 p.m.