Triple
T16261741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC heavyweight division |
E394770
|
entity |
| Predicate | typicalBoutDurationTitle |
P109104
|
FINISHED |
| Object | 5 rounds of 5 minutes |
—
|
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 of 5 minutes | Statement: [UFC heavyweight division, typicalBoutDurationTitle, 5 rounds of 5 minutes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBoutDurationTitle Context triple: [UFC heavyweight division, typicalBoutDurationTitle, 5 rounds of 5 minutes]
-
A.
typicalViewingTime
Indicates the usual or most common amount of time an entity is viewed or watched under normal circumstances.
-
B.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
C.
hasTypicalPerformanceDuration
chosen
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
D.
typicalTourDuration
Indicates the usual length of time that a tour normally takes to complete.
-
E.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c4a0b08190af3574f087205afc |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.