Triple
T33505028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ward–Gatti II |
E858087
|
entity |
| Predicate | sanctioning |
P39509
|
FINISHED |
| Object | non‑title bout |
—
|
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: non‑title bout | Statement: [Ward–Gatti II, sanctioning, non‑title bout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctioning Context triple: [Ward–Gatti II, sanctioning, non‑title bout]
-
A.
sanction
chosen
Indicates the imposition of an official penalty or restrictive measure by an authority in response to certain actions or behaviors.
-
B.
sanctionedAs
Indicates that an entity is officially approved, authorized, or recognized in a particular role, status, or capacity by a relevant authority.
-
C.
sanctionedUnder
Indicates that an action, decision, or status is authorized, approved, or imposed in accordance with a specific rule, law, policy, or regulatory framework.
-
D.
sanctioningStatus
Indicates the current status of formal penalties, restrictions, or sanctions applied to an entity by an authority.
-
E.
sanctioningLevel
Indicates the degree or severity of formal penalties, restrictions, or disciplinary measures imposed in response to a violation or noncompliant behavior.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e59ed5388190b4db22e945b40e20 |
completed | May 3, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.