Triple
T26346400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Alliance |
E662786
|
entity |
| Predicate | keyStorylineEvent |
P259
|
FINISHED |
| Object | Invasion pay-per-view |
—
|
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: Invasion pay-per-view | Statement: [The Alliance, keyStorylineEvent, Invasion pay-per-view]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyStorylineEvent Context triple: [The Alliance, keyStorylineEvent, Invasion pay-per-view]
-
A.
notableStoryEvent
Indicates that an event plays a significant or memorable role within the narrative or storyline associated with the subject.
-
B.
significantEvent
chosen
Indicates that an event involving the entities is of notable importance or impact within a given context.
-
C.
bearerNotableEvent
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
-
D.
significantEventInvolves
Indicates that a significant event includes or engages a particular entity as a participant or key element.
-
E.
keyBattleEvent
Indicates that the event represents a major or decisive moment within a battle or conflict.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 10:42 p.m.