Triple
T8245486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corian |
E192838
|
entity |
| Predicate | cleanedWith |
P4791
|
FINISHED |
| Object | mild detergent 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: mild detergent and water | Statement: [Corian, cleanedWith, mild detergent and water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cleanedWith Context triple: [Corian, cleanedWith, mild detergent 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.
notCleanedFor
Indicates that one entity has not been cleaned, maintained, or cleared in preparation for use by another entity.
-
C.
usesCleanContent
Indicates that one entity employs or relies on content that is free from inappropriate, offensive, or unsafe material.
-
D.
isRinseRequired
Indicates that an item or surface must be rinsed, typically with water, as a required step in a process or procedure.
-
E.
usedWith
chosen
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7872f6d481909ea1d3c2aad1a2b1 |
completed | March 31, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69cb36b437e881909958591357e83b9d |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:48 p.m.