Triple
T35885794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Henderson vs Michael Bisping |
E1037638
|
entity |
| Predicate | HendersonStyle |
P184911
|
FINISHED |
| Object | wrestling-based striker |
—
|
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: wrestling-based striker | Statement: [Dan Henderson vs Michael Bisping, HendersonStyle, wrestling-based striker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HendersonStyle Context triple: [Dan Henderson vs Michael Bisping, HendersonStyle, wrestling-based striker]
-
A.
metricalStyle
Indicates the specific metrical pattern or rhythmic structure used in the form or performance of something.
-
B.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
C.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
D.
riftStyle
Indicates a stylistic or design relationship characterized by features associated with a “rift” (such as a split, fracture, or division) between entities.
-
E.
styleHeldBy
Indicates that a particular style, design, or aesthetic is possessed, used, or embodied by a specific entity.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: May 3, 2026, 4:06 p.m.