Triple
T11094811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lady of the Shroud |
E262348
|
entity |
| Predicate | hasRomanticPlot |
P19974
|
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, hasRomanticPlot, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticPlot Context triple: [The Lady of the Shroud, hasRomanticPlot, yes]
-
A.
hasMarriagePlot
chosen
Indicates that the work’s narrative centrally involves courtship, romantic relationships, or the progression toward marriage as a key plot element.
-
B.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
C.
romanticOutcomeWithJamesBond
Indicates that there is a romantic relationship or romantic outcome involving James Bond and another entity.
-
D.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
E.
romanticTriangleInvolves
Indicates a romantic relationship structure in which three individuals are mutually or asymmetrically involved in overlapping romantic connections.
- 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_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. |
Created at: April 8, 2026, 9:27 p.m.