Triple
T33067318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Perdón |
E846135
|
entity |
| Predicate | hasRomanticNarrative |
P154818
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [El Perdón, hasRomanticNarrative, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticNarrative Context triple: [El Perdón, hasRomanticNarrative, true]
-
A.
hasRomanticPlotline
chosen
Indicates that there is a romantic storyline or relationship development present between the entities.
-
B.
hasRomanticSubplot
Indicates that a work includes a secondary storyline centered on a romantic relationship between characters.
-
C.
hasRomanticEntanglementInPlot
Indicates that a romantic relationship or involvement between characters is a significant element within the narrative plot.
-
D.
hasRomanticMisadventures
Indicates that an entity experiences a series of problematic, comical, or unsuccessful romantic relationships or encounters.
-
E.
hasRomanticSceneAt
Indicates that a romantic scene occurs at a specific location or point in time within a work or context.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:25 a.m.