Triple
T30053449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ken Norton vs. Muhammad Ali I |
E763661
|
entity |
| Predicate | fighter1Style |
P169706
|
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: [Ken Norton vs. Muhammad Ali I, fighter1Style, orthodox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fighter1Style Context triple: [Ken Norton vs. Muhammad Ali I, fighter1Style, orthodox]
-
A.
fighter1StyleDescription
Indicates the descriptive characterization of the fighting style used by the first fighter in a matchup or comparison.
-
B.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
-
C.
fighter2
Indicates that the subject is the second participant (opponent) in a fighting or combat relationship or event.
-
D.
fighter1Trainer
Indicates that one entity serves as the trainer or coach responsible for preparing and guiding the first fighter entity.
-
E.
fighter1Role
Indicates the specific role or function that the first fighter assumes within 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_69f68048391c8190abe6580678f8a9ef |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 6:56 p.m.