Triple
T36153090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC featherweight division |
E1045646
|
entity |
| Predicate | typicalFightDuration |
P195993
|
FINISHED |
| Object | 3 rounds non-title |
—
|
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: 3 rounds non-title | Statement: [UFC featherweight division, typicalFightDuration, 3 rounds non-title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFightDuration Context triple: [UFC featherweight division, typicalFightDuration, 3 rounds non-title]
-
A.
typicalBoutLength
chosen
Indicates the usual or characteristic duration of a single bout or episode of an activity or behavior.
-
B.
battleDuration
Indicates the length of time for which a particular battle or combat event lasts.
-
C.
standardTitleFightRoundDurationMinutes
Indicates the number of minutes that each round lasts in a standard title fight.
-
D.
fightType
Indicates the specific category or style of fight associated with an event or interaction between entities.
-
E.
typicalDurationMinutes
Indicates the usual or expected length of time, measured in minutes, that an event, activity, or process typically lasts.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.