Triple
T33929134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBF bantamweight title |
E869836
|
entity |
| Predicate | previousStandardRoundsLength |
P12056
|
FINISHED |
| Object | 15 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: 15 rounds | Statement: [IBF bantamweight title, previousStandardRoundsLength, 15 rounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStandardRoundsLength Context triple: [IBF bantamweight title, previousStandardRoundsLength, 15 rounds]
-
A.
standardRoundLength
chosen
Indicates that there is a defined, typical duration assigned to a single round within a process, activity, or game.
-
B.
numberOfRoundsToWin
Indicates the number of rounds an entity must win in a competition or game to be declared the overall winner.
-
C.
roundsPerTournament
Indicates the number of rounds that occur within a single tournament.
-
D.
numberedRoundsCharacteristics
Indicates that the entity’s rounds are organized or defined by specific numerical characteristics, such as count, order, or sequence-related properties.
-
E.
roundsStructure
Indicates that one entity defines or specifies the organization, sequence, or format of rounds within a process, event, or system.
- 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_69f3499a59788190bff762a891471b31 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: May 1, 2026, 1:49 a.m.