Triple
T25996669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Middleweight Championship |
E646503
|
entity |
| Predicate | hasOutcomeDeterminedBy |
P161252
|
FINISHED |
| Object | corner retirement |
—
|
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: corner retirement | Statement: [World Middleweight Championship, hasOutcomeDeterminedBy, corner retirement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeDeterminedBy Context triple: [World Middleweight Championship, hasOutcomeDeterminedBy, corner retirement]
-
A.
hasOutcomeDeterminedBy
chosen
Indicates that the result or consequence of one entity is decided, controlled, or directly influenced by another entity.
-
B.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
C.
hasOutcomeClass
Indicates that something is associated with a particular category or type of outcome.
-
D.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
E.
hasConclusion
Indicates that something leads to, results in, or is associated with a particular conclusion.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 22, 2026, 8:58 a.m.