Triple
T22254418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLIPS liquid-infused slippery surfaces |
E550060
|
entity |
| Predicate | canUseLubricantType |
P138698
|
FINISHED |
| Object | silicone oils |
—
|
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: silicone oils | Statement: [SLIPS liquid-infused slippery surfaces, canUseLubricantType, silicone oils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseLubricantType Context triple: [SLIPS liquid-infused slippery surfaces, canUseLubricantType, silicone oils]
-
A.
hasLubricationMethod
Indicates the method or technique by which lubrication is applied or provided in a given context.
-
B.
oilType
Indicates the specific kind or classification of oil associated with an entity.
-
C.
canBeUsed
chosen
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
- 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_69e11e42adb8819087714772ea606709 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f138c1d70881908df47b0f818c0022 |
completed | April 28, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69e72fe1e0cc8190bd13cff2a0846225 |
completed | April 21, 2026, 8:05 a.m. |
Created at: April 16, 2026, 8:39 p.m.