Triple
T23165642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC 4 |
E578704
|
entity |
| Predicate | numberOfSuperfights |
P151173
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [UFC 4, numberOfSuperfights, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfSuperfights Context triple: [UFC 4, numberOfSuperfights, 1]
-
A.
numberOfProfessionalFights
Indicates the total count of professional-level fights associated with an entity (such as a person or competitor).
-
B.
roundsFought
Indicates the number of rounds in which the related entities have engaged in a fight or combat.
-
C.
totalFights
Indicates the total number of fights that have occurred involving the specified entities or within the specified context.
-
D.
numberOfOpponentsBeaten
Indicates the count of distinct opponents that an entity has successfully defeated.
-
E.
laterFightsFor
Indicates that one entity fights on behalf of or in support of another entity at a later time than some referenced point or event.
- 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_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. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:03 p.m.