Triple
T26346791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECW One Night Stand 2006 main event |
E662796
|
entity |
| Predicate | interferenceBy |
P10362
|
FINISHED |
| Object | Edge |
—
|
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: Edge | Statement: [ECW One Night Stand 2006 main event, interferenceBy, Edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interferenceBy Context triple: [ECW One Night Stand 2006 main event, interferenceBy, Edge]
-
A.
hasInterference
Indicates that one entity negatively affects or obstructs the normal function, performance, or occurrence of another entity or process.
-
B.
interactionBetween
Indicates a reciprocal or mutual action, influence, or communication occurring between two or more entities.
-
C.
يتداخل
Indicates that one entity overlaps or intersects spatially, temporally, or conceptually with another entity.
-
D.
interceptedBy
Indicates that an action, communication, or movement is stopped, captured, or diverted by another agent before reaching its intended target or destination.
-
E.
intervenedIn
chosen
Indicates that an entity took action to alter, influence, or interrupt the course of an event, process, or interaction involving other entities.
- 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_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 26, 2026, 10:42 p.m.