Triple
T26765607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ξ*− (dss) |
E674927
|
entity |
| Predicate | hasChargeInElementaryCharges |
P3968
|
FINISHED |
| Object | −1 |
—
|
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: −1 | Statement: [Ξ*− (dss), hasChargeInElementaryCharges, −1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChargeInElementaryCharges Context triple: [Ξ*− (dss), hasChargeInElementaryCharges, −1]
-
A.
hasElectricChargeQuantization
Indicates that the electric charge of an entity can only take on discrete, quantized values rather than varying continuously.
-
B.
isElectricallyNeutral
Indicates that an entity has no net electric charge, with its positive and negative charges balanced.
-
C.
hasChargeConjugation
Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
-
D.
hasElectricCharge
chosen
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
E.
hasChargeConjugationEigenvalue
Indicates that a particle or state possesses a specific eigenvalue under the charge conjugation symmetry operation (i.e., how it transforms when particles are replaced by their antiparticles).
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1c555081908787dbf76147f180 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 27, 2026, 3:59 a.m.