Triple
T16261769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UFC heavyweight division |
E394770
|
entity |
| Predicate | earlyRulesIncludedNoWeightLimit |
P122411
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UFC heavyweight division, earlyRulesIncludedNoWeightLimit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlyRulesIncludedNoWeightLimit Context triple: [UFC heavyweight division, earlyRulesIncludedNoWeightLimit, true]
-
A.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
B.
underRule
Indicates that one entity is governed, controlled, or subject to the authority, rules, or dominion of another entity.
-
C.
usesTimingRules
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
-
D.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
E.
numberOfRulesPlanned
Indicates the planned or intended count of rules associated with an entity or process.
- 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_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. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:04 a.m.