Triple
T20749511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MMA |
E510679
|
entity |
| Predicate | hasChampionshipRounds |
P141355
|
FINISHED |
| Object | 5 rounds |
—
|
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: 5 rounds | Statement: [MMA, hasChampionshipRounds, 5 rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChampionshipRounds Context triple: [MMA, hasChampionshipRounds, 5 rounds]
-
A.
hasChampionshipStage
Indicates that an entity includes or is associated with a particular championship phase or final stage within a competition or series.
-
B.
hasChampionshipGames
Indicates that an entity includes, hosts, or is associated with one or more championship-level games or matches.
-
C.
hasChampionshipMatch
Indicates that an entity is associated with a specific championship-level match, typically as an organizer, participant, or host.
-
D.
hasChampionships
Indicates that one entity possesses or has won one or more championships associated with another entity.
-
E.
hasChampionshipDetermination
Indicates that an entity specifies the rules, criteria, or process by which a championship winner is determined.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c228af288190a20829d45c034c24 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3cbe5788190b7ace43bfdac2ef6 |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 12:34 p.m.