Triple
T26346561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Hardcore Championship |
E662789
|
entity |
| Predicate | titleBeltDesignFeature |
P106151
|
FINISHED |
| Object | broken and taped-up WWF Championship belt |
—
|
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: broken and taped-up WWF Championship belt | Statement: [WWE Hardcore Championship, titleBeltDesignFeature, broken and taped-up WWF Championship belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleBeltDesignFeature Context triple: [WWE Hardcore Championship, titleBeltDesignFeature, broken and taped-up WWF Championship belt]
-
A.
beltFeature
chosen
Indicates that an entity possesses or is characterized by a specific belt-related attribute or component.
-
B.
beltDesign
Indicates a relationship where one entity specifies or defines the design, style, or pattern applied to a belt.
-
C.
beltType
Indicates the specific kind or category of belt associated with an entity.
-
D.
beltDesignOwner
Indicates that a particular entity is the owner or rights holder of a specific belt design.
-
E.
bandDesignation
Indicates that one entity is formally assigned or labeled as belonging to a particular band, group, or category.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 26, 2026, 10:42 p.m.