Triple
T35885792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dan Henderson vs Michael Bisping |
E1037638
|
entity |
| Predicate | HendersonStance |
P8071
|
FINISHED |
| Object | orthodox |
—
|
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: orthodox | Statement: [Dan Henderson vs Michael Bisping, HendersonStance, orthodox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HendersonStance Context triple: [Dan Henderson vs Michael Bisping, HendersonStance, orthodox]
-
A.
HendersonCorner
Indicates a spatial relationship where one location or object is situated at or near a specific corner or junction referred to as "Henderson Corner."
-
B.
bearerStance
Indicates the attitude, position, or viewpoint that the bearer holds toward a referenced subject or issue.
-
C.
hasFightingStance
chosen
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
D.
standsUpTo
Indicates confronting, resisting, or opposing another entity’s actions, demands, or influence, especially in the face of pressure or intimidation.
-
E.
boxingStance
Indicates the specific posture or positioning a boxer adopts while preparing to fight or engage in boxing actions.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.