Triple
T22918659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aquafina |
E568797
|
entity |
| Predicate | treatmentProcess |
P104012
|
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: [Aquafina, treatmentProcess, purification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatmentProcess Context triple: [Aquafina, treatmentProcess, purification]
-
A.
treatment
Indicates that one entity is used as a medical or therapeutic intervention to address, manage, or cure a condition affecting another entity.
-
B.
treatmentOf
Indicates a relationship where one entity administers, provides, or is responsible for a therapeutic intervention directed toward another entity (typically a patient or condition).
-
C.
treatmentType
Indicates the specific kind or category of treatment applied or prescribed in relation to an entity or condition.
-
D.
proposedTreatment
Indicates that one entity is suggested or recommended as a possible treatment or therapeutic intervention for another entity.
-
E.
typicalProcess
chosen
Indicates that the related process is characteristic, usual, or commonly occurring for the given entity or context.
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d316188190901d9356c07110e3 |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.