Triple
T30102758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muhammad Ali–Ken Norton boxing trilogy |
E765041
|
entity |
| Predicate | thirdFightRounds |
P180964
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Muhammad Ali–Ken Norton boxing trilogy, thirdFightRounds, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdFightRounds Context triple: [Muhammad Ali–Ken Norton boxing trilogy, thirdFightRounds, 15]
-
A.
thirdFightState
Indicates the condition or status of the entities involved during the third occurrence of a fight or combat interaction.
-
B.
thirdBoutResult
Indicates the outcome or result of the third bout in a sequence of competitive events or matches.
-
C.
hasThirdRound
Indicates that an entity includes, participates in, or is associated with a third round within a multi-round process or sequence.
-
D.
thirdBettingRoundName
Indicates the designated name or label used for the third betting round in a sequence of betting rounds.
-
E.
thirdFightCountry
Indicates the country where the third fight (in a sequence of fights or matches) takes place or is associated with.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 29, 2026, 7:08 p.m.