Triple
T22058324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvin Hagler vs. Roberto Durán |
E545080
|
entity |
| Predicate | eraRuleSet |
P49971
|
FINISHED |
| Object | 15-round championship distance |
—
|
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: 15-round championship distance | Statement: [Marvin Hagler vs. Roberto Durán, eraRuleSet, 15-round championship distance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraRuleSet Context triple: [Marvin Hagler vs. Roberto Durán, eraRuleSet, 15-round championship distance]
-
A.
eraPolicy
chosen
Indicates that a specific policy was in effect during a particular historical or temporal era.
-
B.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
C.
setsRulesFor
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
D.
eraDefinition
Indicates the specific time period or historical era during which something is defined, classified, or considered valid.
-
E.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285959f48190b89527b3f9e7ab11 |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.