Triple
T30053442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Norton vs. Muhammad Ali I |
E763661
|
entity |
| Predicate | fighter2Injury |
P168392
|
FINISHED |
| Object | broken jaw |
—
|
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: broken jaw | Statement: [Ken Norton vs. Muhammad Ali I, fighter2Injury, broken jaw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighter2Injury Context triple: [Ken Norton vs. Muhammad Ali I, fighter2Injury, broken jaw]
-
A.
fighter2
Indicates that the subject is the second participant (opponent) in a fighting or combat relationship or event.
-
B.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
-
C.
fighter2Description
Indicates the descriptive information or characterization associated with the second fighter in a comparative or relational context.
-
D.
wasWoundedIn
Indicates that an entity sustained an injury as a result of a specified event, situation, or conflict.
-
E.
fighter1Status
Indicates the current condition or state of the first fighter in a combat or competitive context.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67a18676081908488b1e38d156284 |
completed | May 2, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 6:56 p.m.