Triple
T26765421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | up quark |
E674924
|
entity |
| Predicate | electricChargeInCoulombs |
P3968
|
FINISHED |
| Object | approximately +1.07e-19 C |
—
|
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: approximately +1.07e-19 C | Statement: [up quark, electricChargeInCoulombs, approximately +1.07e-19 C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electricChargeInCoulombs Context triple: [up quark, electricChargeInCoulombs, approximately +1.07e-19 C]
-
A.
conversionFromElementaryCharge
Indicates the numerical factor or relationship used to convert a quantity expressed in elementary charges into another unit of electric charge.
-
B.
hasElectricChargeQuantization
Indicates that the electric charge of an entity can only take on discrete, quantized values rather than varying continuously.
-
C.
hasElectricCharge
chosen
Indicates that an entity possesses a nonzero electric charge as a physical property.
-
D.
chargeStoredProportionalTo
Indicates that the amount of charge stored in one entity varies in direct proportion to a specified quantity or property of another entity.
-
E.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 3:59 a.m.