Triple
T1405837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muay Thai |
E31689
|
entity |
| Predicate | protectiveEquipment |
P27649
|
FINISHED |
| Object | boxing gloves |
—
|
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: boxing gloves | Statement: [Muay Thai, protectiveEquipment, boxing gloves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectiveEquipment Context triple: [Muay Thai, protectiveEquipment, boxing gloves]
-
A.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
B.
armourBelt
Indicates a relationship where an armour belt is equipped on, attached to, or associated with an entity (such as a character, vehicle, or structure) as protective gear.
-
C.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
D.
armorType
Indicates the specific category or classification of protective armor associated with an entity.
-
E.
armour
Indicates that an entity provides protective covering or defense for another entity.
- F. None of above. chosen
Provenance (4 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3bc55a08190a4dfe13a5378aff3 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.