Triple
T23165585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 2 |
E578703
|
entity |
| Predicate | tournamentSize |
P67032
|
FINISHED |
| Object | 16-man tournament |
—
|
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: 16-man tournament | Statement: [UFC 2, tournamentSize, 16-man tournament]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentSize Context triple: [UFC 2, tournamentSize, 16-man tournament]
-
A.
leagueSizeContext
Indicates the contextual information or conditions under which the size of a league is defined, measured, or interpreted.
-
B.
capacityAfterTournament
Indicates the resulting capacity of something after a tournament has taken place or been completed.
-
C.
petitionSize
Indicates the number of signatures or participants associated with a given petition.
-
D.
teamMatchPlayBracketSize
chosen
Indicates the number of teams included in the bracket for a team-based match play competition.
-
E.
tournamentBracket
Indicates the structured competitive relationship among participants in a tournament, showing who faces whom and how winners advance through successive rounds.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2bca4881909f6148d588948018 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.