Triple
T2831624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo Creed |
E62249
|
entity |
| Predicate | fightOutcomeWithRockyInRocky |
P34090
|
FINISHED |
| Object | wins by split decision |
—
|
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: wins by split decision | Statement: [Apollo Creed, fightOutcomeWithRockyInRocky, wins by split decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fightOutcomeWithRockyInRocky Context triple: [Apollo Creed, fightOutcomeWithRockyInRocky, wins by split decision]
-
A.
fightNumberForFrazier
Indicates the specific fight number or sequence position of a bout involving Frazier within a series of fights.
-
B.
wonChampionshipAgainst
Indicates that one competitor secured a championship title by defeating another specific opponent.
-
C.
wonAgainst
chosen
Indicates that one entity achieved victory over another in a competition, conflict, or contest.
-
D.
fightingOutOf
Indicates that an individual is competing or representing themselves in a fight or match while being officially associated with a particular location, camp, or organization.
-
E.
facedOpponent
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
- 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_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. |
Created at: March 6, 2026, 10:01 p.m.