Triple
T18716681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Judas Kiss |
E457659
|
entity |
| Predicate | secondActSetting |
P91562
|
FINISHED |
| Object | Villa in Naples |
—
|
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: Villa in Naples | Statement: [The Judas Kiss, secondActSetting, Villa in Naples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondActSetting Context triple: [The Judas Kiss, secondActSetting, Villa in Naples]
-
A.
secondAct
chosen
Indicates that an entity performs, participates in, or is associated with the second act or phase within a larger, ordered sequence of actions or events.
-
B.
secondarySetting
Indicates that an entity serves as an additional or supporting setting context for another entity, rather than being the primary setting.
-
C.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
-
D.
secondEpisode
Indicates that one episode is the immediate successor (second in order) to a preceding episode within the same series or sequence.
-
E.
secondEP
Indicates that an entity is the second episode (EP) in a sequence or series of episodes.
- 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_69d8d393ba9c8190a8b03b04ddbb0a09 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56ab6e0948190b8c70bdea43d2ee5 |
completed | April 19, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69e478e0889c8190a118d67b200ce8ef |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:50 a.m.