Triple
T13433617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWE Intercontinental Championship |
E320172
|
entity |
| Predicate | hasHadMultipleBeltDesigns |
P109909
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WWE Intercontinental Championship, hasHadMultipleBeltDesigns, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHadMultipleBeltDesigns Context triple: [WWE Intercontinental Championship, hasHadMultipleBeltDesigns, true]
-
A.
hasPhysicalBelt
Indicates that one entity possesses or is equipped with a physical belt as an item or feature.
-
B.
usesBeltSystem
Indicates that a subject employs a structured belt-ranking system (e.g., colored belts) to denote levels of skill, progress, or status.
-
C.
hasDifferentFrontDesigns
Indicates that the related entities possess distinct or non-identical designs on their front sides.
-
D.
beltDesignOwner
Indicates that a particular entity is the owner or rights holder of a specific belt design.
-
E.
beltDesign
Indicates a relationship where one entity specifies or defines the design, style, or pattern applied to a belt.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaee29fec81908b07b4fca2922242 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:40 p.m.