Triple
T38114207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croslite foam resin |
E951745
|
entity |
| Predicate | canBeCleanedWith |
P81155
|
FINISHED |
| Object | soap and water |
—
|
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: soap and water | Statement: [Croslite foam resin, canBeCleanedWith, soap and water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCleanedWith Context triple: [Croslite foam resin, canBeCleanedWith, soap and water]
-
A.
cleaningAction
Indicates an action in which an agent removes dirt, impurities, or unwanted substances from a target object, area, or entity.
-
B.
hasCleanlinessLevel
Indicates the degree or state of cleanliness associated with an entity.
-
C.
cleaningProperty
chosen
Indicates that one entity serves as a cleaning-related attribute, method, or characteristic associated with another entity.
-
D.
isRinseRequired
Indicates that an item or surface must be rinsed, typically with water, as a required step in a process or procedure.
-
E.
cleanSweep
Indicates achieving a complete and flawless victory or success in all parts of a competition, task, or series, leaving no losses or omissions.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: May 3, 2026, 4:21 p.m.