Triple
T12306178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBF light welterweight title |
E293357
|
entity |
| Predicate | combatSportType |
P1907
|
FINISHED |
| Object | combat sport |
—
|
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: combat sport | Statement: [IBF light welterweight title, combatSportType, combat sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatSportType Context triple: [IBF light welterweight title, combatSportType, combat sport]
-
A.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
B.
sportCategory
chosen
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
C.
typeOfWrestling
Indicates the specific style or category of wrestling that characterizes a given wrestling activity or event.
-
D.
esportDiscipline
Indicates that one entity is a specific esports game or discipline in which the other entity participates or is involved.
-
E.
sportTypeGoverned
Indicates that a governing body or organization has regulatory authority over a particular type of sport.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.