Triple
T30675408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magik |
E780895
|
entity |
| Predicate | romanticLink |
P121646
|
FINISHED |
| Object | Shadowcat (implied, various continuities) |
—
|
NE NERFINISHED |
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: Shadowcat (implied, various continuities) | Statement: [Magik, romanticLink, Shadowcat (implied, various continuities)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanticLink Context triple: [Magik, romanticLink, Shadowcat (implied, various continuities)]
-
A.
romanticAssociation
chosen
Indicates a romantic relationship or involvement exists between the associated entities.
-
B.
romanticallyObsessedWith
Indicates a strong, often overwhelming romantic fixation or preoccupation that one entity has toward another.
-
C.
romanticArc
Indicates a developing or ongoing romantic relationship or storyline between the involved entities.
-
D.
romanticSubplotCentral
Indicates that a romantic subplot is a primary, driving element of the narrative rather than a minor or peripheral thread.
-
E.
romanticPattern
Indicates a recurring style, tendency, or structure in how romantic relationships or attractions develop or are expressed between entities.
- 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_69f224a7fc208190a07d6d3879b31640 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 8:32 p.m.