Triple
T36697287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolts Program |
E906125
|
entity |
| Predicate | typicallyOpposedBy |
P73168
|
FINISHED |
| Object | traditional superhero teams |
—
|
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: traditional superhero teams | Statement: [Thunderbolts Program, typicallyOpposedBy, traditional superhero teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOpposedBy Context triple: [Thunderbolts Program, typicallyOpposedBy, traditional superhero teams]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedBecause
Indicates that one entity is opposed to another specifically due to a particular reason, cause, or justification.
-
C.
opposedDuring
Indicates that one entity actively resisted or was in conflict with another entity during a specified time period or event.
-
D.
opposedByGroup
chosen
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
-
E.
theoryOpposed
Indicates that one theory stands in opposition to, or conflicts with, another theory.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.