Triple
T36302891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knucklehead |
E893867
|
entity |
| Predicate | featuresProfessionalWrestler |
P49139
|
FINISHED |
| Object | Paul Wight |
E1870698
|
NE 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: Paul Wight | Statement: [Knucklehead, featuresProfessionalWrestler, Paul Wight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProfessionalWrestler Context triple: [Knucklehead, featuresProfessionalWrestler, Paul Wight]
-
A.
featuredWrestler
chosen
Indicates that a particular wrestler is highlighted or prominently showcased in a given context or event.
-
B.
associatedWrestler
Indicates that one entity is connected or linked to a particular wrestler, typically through participation, representation, or relevant involvement.
-
C.
promotedWrestler
Indicates that one entity advanced, advertised, or otherwise publicly supported the wrestling career or appearances of another entity.
-
D.
managedWrestler
Indicates that one entity served as the manager of another entity in a professional wrestling context.
-
E.
featuredFighter
Indicates that a particular fighter is highlighted or prominently showcased in a given context or event.
- F. None of above.
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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfb83e848190b1f70dc2deebce10 |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.