Triple
T5277074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rogue |
E119394
|
entity |
| Predicate | formerAlignment |
P26427
|
FINISHED |
| Object | villain |
—
|
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: villain | Statement: [Rogue, formerAlignment, villain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerAlignment Context triple: [Rogue, formerAlignment, villain]
-
A.
previousAlignment
chosen
Indicates that one entity’s alignment or orientation occurred earlier in time than another’s.
-
B.
originallyAlignedWith
Indicates that an entity was initially in agreement, support, or association with another entity or group, regardless of any later changes in stance or affiliation.
-
C.
alignedAgainst
Indicates that two or more entities are united in opposition to a common target, side, or objective.
-
D.
realignedFrom
Indicates that something has been adjusted or repositioned from a previous alignment, configuration, or orientation to a new one.
-
E.
basedOnAlignmentOf
Indicates a relationship where one entity is determined, derived, or decided according to how closely it aligns with another entity’s position, orientation, or criteria.
- 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_69bd446d05a8819092ad333a3f9c8d5c |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8c9c72b08190947b6b955ac1bb5a |
completed | March 20, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69bd844a56b48190ad743c42246e02dd |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:51 p.m.