Triple
T31572448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Heavyweight Championship boxing matches |
E805600
|
entity |
| Predicate | decisionTypesInclude |
P175812
|
FINISHED |
| Object | knockout |
—
|
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: knockout | Statement: [World Heavyweight Championship boxing matches, decisionTypesInclude, knockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionTypesInclude Context triple: [World Heavyweight Championship boxing matches, decisionTypesInclude, knockout]
-
A.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
B.
includesDecisionsBy
Indicates that something contains, encompasses, or takes into account decisions made by a specified party or set of parties.
-
C.
includesDecisionOn
Indicates that one item or process contains, encompasses, or explicitly addresses a particular decision or determination.
-
D.
decisionMakerType
Indicates the role or category of entity responsible for making a particular decision.
-
E.
decisionTypeReviewed
Indicates that a particular decision has been examined or evaluated, typically as part of a review or oversight process.
- 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: April 30, 2026, 10:20 p.m.