Triple
T35208212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhandle Slam |
E1016597
|
entity |
| Predicate | ringStyleAssociation |
P88470
|
FINISHED |
| Object | WWE main-event style |
—
|
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: WWE main-event style | Statement: [Manhandle Slam, ringStyleAssociation, WWE main-event style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ringStyleAssociation Context triple: [Manhandle Slam, ringStyleAssociation, WWE main-event style]
-
A.
ringType
Indicates the specific kind or category of ring associated with an entity or relationship.
-
B.
usesRingStyle
chosen
Indicates that one entity performs or operates using a particular ring-based style, method, or format.
-
C.
associatedWithRing
Indicates that an entity has a connection or relationship with a specific ring, such as ownership, membership, or involvement.
-
D.
ringSize
Indicates the size or measurement of a ring associated with an entity.
-
E.
ringOrigin
Indicates the source or starting point from which a ring (such as a circular structure, feature, or formation) arises or is generated.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.