Triple
T21005089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinister Six |
E517393
|
entity |
| Predicate | primaryOpposes |
P50211
|
FINISHED |
| Object | superheroes |
—
|
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: superheroes | Statement: [Sinister Six, primaryOpposes, superheroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpposes Context triple: [Sinister Six, primaryOpposes, superheroes]
-
A.
primaryOpposition
chosen
Indicates the main or most significant opposing relationship between two entities, such as their chief rival, counterforce, or contrasting position.
-
B.
primaryOppositionArc
Indicates the main adversarial or conflicting relationship that drives the central tension or struggle between two entities.
-
C.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
D.
theoryOpposed
Indicates that one theory stands in opposition to, or conflicts with, another theory.
-
E.
opposesLabel
Indicates that one entity expresses disagreement with, resistance to, or active opposition against another entity or its position.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3b25ec8190aa4530d1f0bb2b9e |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:52 p.m.