Triple
T11205508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yang monopole |
E265148
|
entity |
| Predicate | chargeQuantization |
P68589
|
FINISHED |
| Object | topologically quantized |
—
|
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: topologically quantized | Statement: [Yang monopole, chargeQuantization, topologically quantized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeQuantization Context triple: [Yang monopole, chargeQuantization, topologically quantized]
-
A.
conversionFromElementaryCharge
Indicates the numerical factor or relationship used to convert a quantity expressed in elementary charges into another unit of electric charge.
-
B.
magneticChargeQuantization
chosen
Indicates that the magnetic charge of an entity can only take on discrete, quantized values rather than varying continuously.
-
C.
chargeCarrier
Indicates that an entity functions as the primary carrier of electric charge in or for another entity.
-
D.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
E.
chargeParity
Indicates that two related entities share the same electric charge sign (parity), such as both being positively or both negatively charged.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d4eef88190a7f05bca82d919b9 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.