Triple
T2831625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Creed |
E62249
|
entity |
| Predicate | fightOutcomeWithRockyInRockyII |
P42736
|
FINISHED |
| Object | loses by 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: loses by knockout | Statement: [Apollo Creed, fightOutcomeWithRockyInRockyII, loses by knockout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightOutcomeWithRockyInRockyII Context triple: [Apollo Creed, fightOutcomeWithRockyInRockyII, loses by knockout]
-
A.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
B.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
C.
fightNumberForFrazier
Indicates the specific fight number or sequence position of a bout involving Frazier within a series of fights.
-
D.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdebe95188190bf65fb4cd88e2ec5 |
completed | March 7, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_69abdd0acab881909e8c25cbef83678c |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abddccd50c8190a975942f46cfc01f |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:01 p.m.