Triple
T33121890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Warriors |
E847621
|
entity |
| Predicate | targetThreatsOftenOverlookedBy |
P133105
|
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: [New Warriors, targetThreatsOftenOverlookedBy, Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetThreatsOftenOverlookedBy Context triple: [New Warriors, targetThreatsOftenOverlookedBy, Avengers]
-
A.
targetsThreat
chosen
Indicates that one entity is directing an action or focus specifically toward a perceived threat.
-
B.
laterThreat
Indicates that one entity poses a threat to another at a time subsequent to some referenced or initial point.
-
C.
threatTypeEncountered
Indicates that an entity has come across or experienced a specific type of threat.
-
D.
hasThreats
Indicates that one entity poses or is associated with potential danger, harm, or adverse consequences toward another entity.
-
E.
targetOfThreat
Indicates that one entity is the recipient or intended victim of a threat made 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:27 a.m.