Triple
T21588179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC Fight Island 1 |
E532706
|
entity |
| Predicate | otherBoutsIncluded |
P144059
|
FINISHED |
| Object | preliminary card |
—
|
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: preliminary card | Statement: [UFC Fight Island 1, otherBoutsIncluded, preliminary card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherBoutsIncluded Context triple: [UFC Fight Island 1, otherBoutsIncluded, preliminary card]
-
A.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
B.
battleOpponent
Indicates that two entities are engaged in or designated as opponents in a battle or combat scenario.
-
C.
featuredBout
Indicates that a particular bout or match is highlighted or given special prominence within a card, event, or collection of bouts.
-
D.
totalFights
Indicates the total number of fights that have occurred involving the specified entities or within the specified context.
-
E.
followedBattle
Indicates that one battle occurred after and as a consequence or continuation of another battle.
- 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_69e0c46251648190876f0427cf2d321b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb621ab88190a33a943424ffb306 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63384a8fc819084c596bb53a3a1db |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 16, 2026, 6:31 p.m.