Triple
T35527614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Big Show |
E1026712
|
entity |
| Predicate | worldTitleHeldIn |
P8352
|
FINISHED |
| Object | WCW World Heavyweight Championship |
—
|
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: WCW World Heavyweight Championship | Statement: [The Big Show, worldTitleHeldIn, WCW World Heavyweight Championship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldTitleHeldIn Context triple: [The Big Show, worldTitleHeldIn, WCW World Heavyweight Championship]
-
A.
worldTitleHeld
chosen
Indicates that an entity holds or has held a world-level title or championship in a particular domain or competition.
-
B.
titleHeldIn
Indicates that a particular title or position is held within a specified organization, jurisdiction, or contextual domain.
-
C.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
-
D.
heldTitleUnder
Indicates that one entity possessed or occupied a particular title, rank, or office under the authority, jurisdiction, or auspices of another entity.
-
E.
titleHeldInRegion
Indicates that a specific title or rank is held or recognized within a particular geographic or administrative region.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:04 p.m.