Triple
T25002042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vince Russo |
E625739
|
entity |
| Predicate | bookedForWrestler |
P157532
|
FINISHED |
| Object | Steve Austin |
—
|
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: Steve Austin | Statement: [Vince Russo, bookedForWrestler, Steve Austin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookedForWrestler Context triple: [Vince Russo, bookedForWrestler, Steve Austin]
-
A.
wrestledFor
Indicates that one entity engaged in a wrestling match or competition on behalf of, or as a representative of, another entity (such as a team, organization, or country).
-
B.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling context.
-
C.
wrestledWith
Indicates that one entity engaged in a physical wrestling contest or struggle with another entity.
-
D.
wrestledForPromotion
Indicates that one entity engaged in a wrestling match or competitive struggle with another in order to gain a promotion or advancement.
-
E.
wrestlingPromotionAppearedIn
Indicates that a wrestler or wrestling-related entity made an appearance in a specific wrestling promotion or organization.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b0bf1a081908b202efe0fcb73cf |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:05 a.m.