Triple
T1370313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Featherweight Title |
E30098
|
entity |
| Predicate | isContestedIn |
P8400
|
FINISHED |
| Object | professional boxing |
—
|
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: professional boxing | Statement: [World Featherweight Title, isContestedIn, professional boxing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContestedIn Context triple: [World Featherweight Title, isContestedIn, professional boxing]
-
A.
wasContestedIn
chosen
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
numberOfSeatsContested
Indicates the total count of seats in an election or contest that are being competed for or are up for selection.
-
D.
titleContested
Indicates that the legitimacy or ownership of a title is disputed between parties.
-
E.
hasElectionsFor
Indicates that a governing body, jurisdiction, or organization conducts elections to select or appoint members to a specified office, role, or representative body.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d7b6008190bc0303b56959ba56 |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.