Triple
T1789761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suavitel |
E39467
|
entity |
| Predicate | usageStage |
P2529
|
FINISHED |
| Object | rinse cycle of washing machine |
—
|
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: rinse cycle of washing machine | Statement: [Suavitel, usageStage, rinse cycle of washing machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageStage Context triple: [Suavitel, usageStage, rinse cycle of washing machine]
-
A.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
D.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.