Triple
T11094812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lady of the Shroud |
E262348
|
entity |
| Predicate | hasPoliticalPlot |
P97194
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [The Lady of the Shroud, hasPoliticalPlot, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalPlot Context triple: [The Lady of the Shroud, hasPoliticalPlot, yes]
-
A.
allegedPlots
Indicates that one entity is accused or suspected of planning or conspiring to carry out harmful or illicit actions involving another entity.
-
B.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
C.
hasPoliticalDialogue
Indicates that there is an exchange or interaction between entities involving political topics, issues, or negotiations.
-
D.
hasPoliticalBureau
Indicates that an entity possesses or is associated with a political bureau as part of its organizational or governance structure.
-
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. 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0783e88190aae3d461730c2d70 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750ca52ec8190a559432a5de106fd |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.