Triple
T95281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W boson |
E1916
|
entity |
| Predicate | hasChargeConjugation |
P3975
|
FINISHED |
| Object | not an eigenstate of 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: not an eigenstate of C | Statement: [W boson, hasChargeConjugation, not an eigenstate of C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChargeConjugation Context triple: [W boson, hasChargeConjugation, not an eigenstate of C]
-
A.
charge
Indicates that one entity formally accuses another of an offense or imposes a financial cost or obligation on them.
-
B.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
C.
hasCheckAndBalanceWith
Indicates that two entities mutually monitor, limit, or counterbalance each other's powers or actions to prevent dominance or abuse.
-
D.
hasEccentricity
Indicates that an object or orbit possesses a specific degree of deviation from being perfectly circular, quantified by its eccentricity value.
-
E.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebb3da08190a8b82564f33cde3b |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a24fed6b8c819080a6c0cd3b16e6bd |
completed | Feb. 28, 2026, 2:16 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.