Triple
T15833737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plasmacluster |
E383932
|
entity |
| Predicate | effectClaimed |
P73867
|
FINISHED |
| Object | breakdown of airborne contaminants |
—
|
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: breakdown of airborne contaminants | Statement: [Plasmacluster, effectClaimed, breakdown of airborne contaminants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectClaimed Context triple: [Plasmacluster, effectClaimed, breakdown of airborne contaminants]
-
A.
claimsEffect
chosen
Indicates that one entity asserts or states that another entity has a particular effect or impact.
-
B.
usedToClaim
Indicates that something is employed as evidence, justification, or support in making a particular claim.
-
C.
claimedSee
Indicates that one entity asserted or reported having seen or visually perceived another entity or event.
-
D.
alsoClaimedBy
Indicates that the same item, statement, or resource is asserted or claimed by an additional party besides the primary one.
-
E.
claimedFor
Indicates that one entity has asserted ownership, responsibility, or entitlement over or on behalf 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e6670d48190a456581dd951f168 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.