Triple
T35629590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 80 |
E1029546
|
entity |
| Predicate | hasFighterOnCard |
P109204
|
FINISHED |
| Object | B.J. Penn |
—
|
NE NERFINISHED |
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: B.J. Penn | Statement: [UFC 80, hasFighterOnCard, B.J. Penn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFighterOnCard Context triple: [UFC 80, hasFighterOnCard, B.J. Penn]
-
A.
hasFighter
Indicates that an entity possesses, controls, or is associated with a fighter (such as a combatant, combat vehicle, or fighting unit).
-
B.
hasFighterInRedCorner
Indicates that a specified match or event has a particular fighter assigned to the red corner.
-
C.
fighterOnCard
chosen
Indicates that a particular fighter is scheduled to appear on a specific fight card or event lineup.
-
D.
isSupercardOf
Indicates that one card or set of cards fully contains or extends the content, scope, or functionality of another card, making it a more comprehensive or encompassing version.
-
E.
hasFightingMoniker
Indicates that an entity is known by a specific nickname or title used in a fighting or combat context.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: May 3, 2026, 4:05 p.m.