Triple
T27273182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donald Nordley |
E688111
|
entity |
| Predicate | hasRomanticEntanglementInPlot |
P176284
|
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: [Donald Nordley, hasRomanticEntanglementInPlot, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanticEntanglementInPlot Context triple: [Donald Nordley, hasRomanticEntanglementInPlot, yes]
-
A.
hasRomanticPlotline
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.
hasRomanticMisadventures
Indicates that an entity experiences a series of problematic, comical, or unsuccessful romantic relationships or encounters.
-
D.
hasRomanticTensionWith
Indicates a mutual or one-sided romantic attraction or unresolved romantic interest existing between two entities.
-
E.
romanticSubplotCentral
Indicates that a romantic subplot is a primary, driving element of the narrative rather than a minor or peripheral thread.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 27, 2026, 11 a.m.