Triple
T35805434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batista vs Triple H |
E1035089
|
entity |
| Predicate | impactOnBatista |
P47033
|
FINISHED |
| Object | established as main-event star |
—
|
LITERAL FINISHED |
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: established as main-event star | Statement: [Batista vs Triple H, impactOnBatista, established as main-event star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactOnBatista Context triple: [Batista vs Triple H, impactOnBatista, established as main-event star]
-
A.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
B.
impactOnLeader
chosen
Indicates that one entity has an effect, influence, or consequence on a leader within a given context.
-
C.
impactOnField
Indicates the effect or influence that one entity, action, or development has on a particular field or domain.
-
D.
impactOnComics
Indicates the influence or effect that one entity has on the development, content, style, or reception of comics.
-
E.
impactPosition
Indicates the specific location or coordinates at which an impact or collision occurs between 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.