Triple
T15508881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WBO super bantamweight title |
E368652
|
entity |
| Predicate | beltInsignia |
P106151
|
FINISHED |
| Object | WBO logo |
—
|
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: WBO logo | Statement: [WBO super bantamweight title, beltInsignia, WBO logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beltInsignia Context triple: [WBO super bantamweight title, beltInsignia, WBO logo]
-
A.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
B.
beltFeature
chosen
Indicates that an entity possesses or is characterized by a specific belt-related attribute or component.
-
C.
rankInsigniaWornOn
Indicates the physical location on a uniform or body where a rank insignia is displayed or attached.
-
D.
beltRepresents
Indicates that a belt symbolizes, signifies, or stands for a particular concept, status, or meaning in a given context.
-
E.
beltDesign
Indicates a relationship where one entity specifies or defines the design, style, or pattern applied to a belt.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03fd008708190a3657863eb9ac626 |
completed | April 16, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:55 a.m.