Triple
T29942097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lethal Legion |
E760525
|
entity |
| Predicate | recurringAdversariesOf |
P11706
|
FINISHED |
| Object | Avengers |
—
|
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: Avengers | Statement: [Lethal Legion, recurringAdversariesOf, Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringAdversariesOf Context triple: [Lethal Legion, recurringAdversariesOf, Avengers]
-
A.
otherAdversary
Indicates that one entity is an adversary of another, distinct from any primary or previously identified adversary.
-
B.
notableAdversary
chosen
Indicates that one entity is recognized as a significant or prominent opponent or rival of another entity.
-
C.
laterEnemyOf
Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
-
D.
notableAdversaryFormation
Indicates the formation or establishment of a significant opposing force, rival group, or adversarial entity in relation to another.
-
E.
oftenAttackedBy
Indicates that an entity is frequently the target of attacks carried out by another entity.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6780791108190bfec07f0d7119674 |
completed | May 2, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:23 p.m.