Triple
T13242867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intercontinental Championship (defended on associated SmackDown) |
E315322
|
entity |
| Predicate | beltFunction |
P108714
|
FINISHED |
| Object | visual representation of championship status |
—
|
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: visual representation of championship status | Statement: [Intercontinental Championship (defended on associated SmackDown), beltFunction, visual representation of championship status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beltFunction Context triple: [Intercontinental Championship (defended on associated SmackDown), beltFunction, visual representation of championship status]
-
A.
beltFeature
Indicates that an entity possesses or is characterized by a specific belt-related attribute or component.
-
B.
beltType
Indicates the specific kind or category of belt associated with an entity.
-
C.
beltMaterial
Indicates the material from which a belt is made.
-
D.
beltDesign
Indicates a relationship where one entity specifies or defines the design, style, or pattern applied to a belt.
-
E.
collarFeature
Indicates that one entity has a specific characteristic, detail, or attribute related to a collar.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d59e84c8190a9e547d0fe26a5f9 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:23 p.m.