Triple
T30719237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Backlash 2023 |
E782105
|
entity |
| Predicate | stableInvolved |
P170067
|
FINISHED |
| Object | The Bloodline |
—
|
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: The Bloodline | Statement: [WWE Backlash 2023, stableInvolved, The Bloodline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stableInvolved Context triple: [WWE Backlash 2023, stableInvolved, The Bloodline]
-
A.
stillInvolvedIn
Indicates that an entity continues to participate in or be associated with a particular activity, role, or relationship at the present time.
-
B.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
C.
involvedResolution
Indicates that an entity participated in or contributed to the process of resolving a particular issue, conflict, or problem.
-
D.
passInvolved
Indicates that an entity is involved in a passing action, either as the passer, receiver, or otherwise participating party.
-
E.
fortInvolved
Indicates that a fort is involved or participates in a particular event, action, or relationship between entities.
- 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c583438819093b812f11327eb60 |
completed | May 2, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:36 p.m.