Triple
T29783528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pascal Sauvage |
E756193
|
entity |
| Predicate | plotsTo |
P167873
|
FINISHED |
| Object | seize the British throne |
—
|
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: seize the British throne | Statement: [Pascal Sauvage, plotsTo, seize the British throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plotsTo Context triple: [Pascal Sauvage, plotsTo, seize the British throne]
-
A.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
B.
plotter
Indicates that one entity is a device or tool used by another entity to produce precise graphical or plotted output.
-
C.
usesChartsOf
Indicates that one entity employs or relies on the charts, diagrams, or graphical representations provided by another entity.
-
D.
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).
-
E.
producedFigure
Indicates that one entity created or generated a particular figure, illustration, or visual representation.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f674a897c88190a9e671b2a47b57bb |
completed | May 2, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 29, 2026, 5:07 p.m.