Triple
T26765599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ξ*− (dss) |
E674927
|
entity |
| Predicate | hasIntrinsicParityP |
P91257
|
FINISHED |
| Object | + |
—
|
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: + | Statement: [Ξ*− (dss), hasIntrinsicParityP, +]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntrinsicParityP Context triple: [Ξ*− (dss), hasIntrinsicParityP, +]
-
A.
hasIntrinsicParity
chosen
Indicates that an entity possesses a specific intrinsic parity value characterizing its behavior under spatial inversion.
-
B.
hasGParity
Indicates that a particle possesses a specific value of G-parity, describing its behavior under the combined operation of charge conjugation and isospin rotation.
-
C.
hasParity
Indicates that two entities share the same parity property (e.g., both even or both odd) with respect to a specified attribute or value.
-
D.
hasSpinParity
Indicates that a particle or system possesses a specific spin parity value characterizing its combined spin and intrinsic symmetry properties.
-
E.
hasFixedParityWith
Indicates that two entities share the same parity property (e.g., both even or both odd) and thus their parity remains consistently matched.
- 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_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 3:59 a.m.