Triple
T37445274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Al Rihla |
E930526
|
entity |
| Predicate | hasBladderMaterial |
P1845
|
FINISHED |
| Object | rubber bladder |
—
|
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: rubber bladder | Statement: [Adidas Al Rihla, hasBladderMaterial, rubber bladder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBladderMaterial Context triple: [Adidas Al Rihla, hasBladderMaterial, rubber bladder]
-
A.
hasBedMaterial
Indicates that one entity has, contains, or is characterized by a particular bed material (e.g., the substance forming the base or bedding of that entity).
-
B.
hasMaterialType
chosen
Indicates that something is composed of, made from, or characterized by a specific type of material.
-
C.
usesSupportMaterial
Indicates that an entity relies on or incorporates additional supporting materials or resources to carry out an action or fulfill a function.
-
D.
usesMaterialBy
Indicates that one entity makes use of or employs a material that is provided, specified, or created by another entity.
-
E.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.