Triple
T20742060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morrigan |
E510464
|
entity |
| Predicate | romanceOptionFor |
P10693
|
FINISHED |
| Object | male human Warden |
—
|
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: male human Warden | Statement: [Morrigan, romanceOptionFor, male human Warden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanceOptionFor Context triple: [Morrigan, romanceOptionFor, male human Warden]
-
A.
encouragesRomanceBetween
Indicates that one entity promotes, supports, or fosters a romantic relationship between two other entities.
-
B.
romanticOutcome
Indicates that a romantic relationship or interaction between entities results in a particular outcome, such as success, failure, or change in status.
-
C.
romanticPattern
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
-
D.
romanticArc
chosen
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
E.
romanceObstructedBy
Indicates that a romantic relationship or potential romance is being hindered, blocked, or prevented by some opposing factor or circumstance.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c20f9670819082199de21a8d9818 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:33 p.m.