Triple
T37715233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inferno (Marvel Comics crossover) |
E939438
|
entity |
| Predicate | affectsStatusQuoOf |
P190551
|
FINISHED |
| Object | New Mutants |
—
|
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: New Mutants | Statement: [Inferno (Marvel Comics crossover), affectsStatusQuoOf, New Mutants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectsStatusQuoOf Context triple: [Inferno (Marvel Comics crossover), affectsStatusQuoOf, New Mutants]
-
A.
alsoAffects
Indicates that an action, condition, or change impacting one entity additionally impacts another entity as well.
-
B.
affectsBehaviorOf
Indicates that one entity produces a change or influence on the behavior, actions, or conduct of another entity.
-
C.
affectsRelationshipBetween
Indicates that one entity causes a change or influence on the nature, quality, or status of the relationship between two or more other entities.
-
D.
standAffected
Indicates that an entity is in a state or position of being impacted or influenced by another entity or event.
-
E.
areAffectedBy
Indicates that one entity experiences an effect, influence, or impact as a result of another entity or event.
- F. None of above. chosen
Provenance (4 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7779d248190afdb348a95375443 |
completed | May 7, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
| PDg | Predicate description generation | batch_69fcc73264e08190b0b5917f32226fae |
completed | May 7, 2026, 5:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.