Triple
T12399335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tony |
E296204
|
entity |
| Predicate | hasLoveStoryAsCentralPlot |
P19974
|
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: [Tony, hasLoveStoryAsCentralPlot, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLoveStoryAsCentralPlot Context triple: [Tony, hasLoveStoryAsCentralPlot, true]
-
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.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
-
C.
hasSpouseInStory
Indicates that one entity is depicted as the spouse of another within the context of a particular story or narrative.
-
D.
storyline
Indicates that one entity serves as the narrative plot or sequence of events associated with another entity.
-
E.
romanticOutcome
Indicates that a romantic relationship or interaction between entities results in a particular outcome, such as success, failure, or change in status.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd448f08190af425a569d7ed158 |
completed | April 10, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69d93ed4cea08190ad374d3f6a798053 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:55 p.m.