Triple
T21752614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pure Life |
E536950
|
entity |
| Predicate | hasQualityControlProcess |
P83518
|
FINISHED |
| Object | purification |
—
|
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: purification | Statement: [Pure Life, hasQualityControlProcess, purification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQualityControlProcess Context triple: [Pure Life, hasQualityControlProcess, purification]
-
A.
hasQualityControl
chosen
Indicates that an entity is subject to processes or measures designed to monitor, verify, and maintain the quality of its outputs or operations.
-
B.
hasQualityAssuranceModel
Indicates that an entity is associated with or governed by a specific quality assurance model or framework.
-
C.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
-
D.
hasSurfaceQuality
Indicates that one entity possesses a particular characteristic or condition of its surface.
-
E.
qualityAssuranceBody
Indicates that one entity serves as the quality assurance body responsible for evaluating, monitoring, or certifying the standards or performance of 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8b8b9c8190b1f6a8bc25d69dbb |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.