Triple
T34250630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barone di Champigny |
E878730
|
entity |
| Predicate | partOfPlotType |
P103369
|
FINISHED |
| Object | farcical plot |
—
|
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: farcical plot | Statement: [Barone di Champigny, partOfPlotType, farcical plot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfPlotType Context triple: [Barone di Champigny, partOfPlotType, farcical plot]
-
A.
partOfPlot
chosen
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
B.
settingInPlot
Indicates that a particular setting or location serves as the backdrop or environment in which the events of a plot take place.
-
C.
usedInPlot
Indicates that something (e.g., an object, idea, or element) is employed as a component or device within the storyline or narrative structure of a plot.
-
D.
centralPlotDevice
Indicates that one entity functions as the main narrative mechanism or element around which the plot of the other entity is structured.
-
E.
plotInvolvement
Indicates that an entity participates in, contributes to, or is affected by the events or storyline of a narrative work.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00383e868c819098fd17e25fcbdb04 |
completed | May 10, 2026, 7:48 a.m. |
| PD | Predicate disambiguation | batch_6a0037cc59688190b7b9da939a413db3 |
completed | May 10, 2026, 7:46 a.m. |
Created at: May 1, 2026, 1:56 a.m.