Triple
T28533339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electron Proton Alpha Monitor |
E722097
|
entity |
| Predicate | detectsChargeSign |
P164869
|
FINISHED |
| Object | positive ions |
—
|
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: positive ions | Statement: [Electron Proton Alpha Monitor, detectsChargeSign, positive ions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectsChargeSign Context triple: [Electron Proton Alpha Monitor, detectsChargeSign, positive ions]
-
A.
hasElectricCharge
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
B.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
C.
hasChargePosition
Indicates that one entity occupies or is assigned to a particular official role, office, or position of responsibility within another entity.
-
D.
canCharge
Indicates that one entity has the ability or permission to charge another entity, typically in the sense of applying a cost, fee, or electrical charge.
-
E.
containsCharge
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
- F. None of above. chosen
Provenance (4 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 3:30 a.m.