Triple
T30849617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avengers: X-Sanction |
E785741
|
entity |
| Predicate | setsUpEvent |
P170565
|
FINISHED |
| Object | Avengers vs. X-Men |
—
|
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 vs. X-Men | Statement: [Avengers: X-Sanction, setsUpEvent, Avengers vs. X-Men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsUpEvent Context triple: [Avengers: X-Sanction, setsUpEvent, Avengers vs. X-Men]
-
A.
setInEvent
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
B.
preparesForEvent
Indicates that one entity performs actions or makes arrangements in anticipation of a specific event.
-
C.
settingAfterEvent
Indicates that a particular setting or state occurs subsequent to, and as a result of or in temporal sequence with, a specified event.
-
D.
regulatesEvent
Indicates that one entity controls, influences, or modulates the occurrence, timing, or intensity of an event.
-
E.
setAgainstEvent
Indicates that one event is positioned or framed in opposition or contrast to another 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6917b68108190a29980ebda0a62c9 |
completed | May 3, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:46 p.m.