Triple
T16810686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCW World Heavyweight Championship |
E408598
|
entity |
| Predicate | beltDesignFeature |
P106151
|
FINISHED |
| Object | large central plate with WCW logo |
—
|
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: large central plate with WCW logo | Statement: [WCW World Heavyweight Championship, beltDesignFeature, large central plate with WCW logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beltDesignFeature Context triple: [WCW World Heavyweight Championship, beltDesignFeature, large central plate with WCW logo]
-
A.
beltDesign
Indicates a relationship where one entity specifies or defines the design, style, or pattern applied to a belt.
-
B.
beltFeature
chosen
Indicates that an entity possesses or is characterized by a specific belt-related attribute or component.
-
C.
beltDesignOwner
Indicates that a particular entity is the owner or rights holder of a specific belt design.
-
D.
beltDesignChanges
Indicates that modifications have been made to the design or configuration of a belt.
-
E.
ribbonDesignFeature
Indicates a design-related characteristic or attribute that is specifically associated with a ribbon.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cf680c8190bcd640570c524918 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.