Triple
T19372538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 20 Mule Team Borax |
E484577
|
entity |
| Predicate | targetUseEnvironment |
P13408
|
FINISHED |
| Object | household |
—
|
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: household | Statement: [20 Mule Team Borax, targetUseEnvironment, household]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUseEnvironment Context triple: [20 Mule Team Borax, targetUseEnvironment, household]
-
A.
usedInEnvironment
chosen
Indicates that something is utilized or operates within a particular environment or context.
-
B.
hasEnvironmentalTarget
Indicates that an entity has a specified environmental objective, goal, or target it aims to achieve or comply with.
-
C.
supportsEnvironment
Indicates that one entity provides the necessary conditions, compatibility, or resources for another entity to operate or exist within a particular environment.
-
D.
launchEnvironment
Indicates the specific context, configuration, or setting in which a launch or deployment action takes place.
-
E.
environmentalMode
Indicates that an entity operates in or is configured to a specific environmental setting or condition (such as eco, normal, or high-performance mode).
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619b1b5fc819089f9fc43f407bbb0 |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.