Triple
T14601769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dueling Cavalier |
E342720
|
entity |
| Predicate | problemInPlot |
P115001
|
FINISHED |
| Object | poor synchronization of sound |
—
|
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: poor synchronization of sound | Statement: [The Dueling Cavalier, problemInPlot, poor synchronization of sound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: problemInPlot Context triple: [The Dueling Cavalier, problemInPlot, poor synchronization of sound]
-
A.
partOfPlot
Indicates that one event, action, or element is a constituent component within the overall plot of a narrative.
-
B.
problemStatement
Indicates that an entity presents, defines, or expresses a specific problem or issue to be addressed.
-
C.
taskInPlot
Indicates that a specific task occurs within, is associated with, or is part of a particular plot or storyline.
-
D.
problemType
Indicates the specific category or classification of a problem within a defined problem space or system.
-
E.
problems
Indicates that one entity has issues, difficulties, or complications associated with or caused by another entity.
- F. None of above. chosen
Provenance (4 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb438748081908020ce04b869866a |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.