Triple
T35808180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Boss |
E1035156
|
entity |
| Predicate | hasInRingStyle |
P88470
|
FINISHED |
| Object | technical wrestling |
—
|
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: technical wrestling | Statement: [The Boss, hasInRingStyle, technical wrestling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInRingStyle Context triple: [The Boss, hasInRingStyle, technical wrestling]
-
A.
usesRingStyle
chosen
Indicates that one entity performs or operates using a particular ring-based style, method, or format.
-
B.
hasRingAttireType
Indicates the type or style of clothing or gear an entity wears specifically for performing or competing in the ring.
-
C.
hasRing
Indicates that one entity possesses, wears, or is characterized by the presence of a ring.
-
D.
showRingStyle
Indicates that one entity presents or displays the style or design characteristics of a ring to another entity.
-
E.
hasRingRegion
Indicates that one entity possesses or includes a ring-shaped region as part of its structure or spatial extent.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a007fc9d9688190af411d5841af34be |
completed | May 10, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_6a007f64813081909a2950336402073b |
completed | May 10, 2026, 12:51 p.m. |
Created at: May 3, 2026, 4:06 p.m.