Triple
T26857235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xi- baryon |
E676228
|
entity |
| Predicate | hasIsospinProjection |
P23050
|
FINISHED |
| Object | -1/2 |
—
|
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/2 | Statement: [Xi- baryon, hasIsospinProjection, -1/2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIsospinProjection Context triple: [Xi- baryon, hasIsospinProjection, -1/2]
-
A.
hasIsospin
Indicates that one particle possesses a specific isospin value or quantum number in relation to another reference or classification framework.
-
B.
hasIsospinMultiplet
Indicates that two or more particles belong to the same isospin multiplet, i.e., they are related by isospin symmetry and differ only in their isospin projection (such as charge states).
-
C.
hasIsospinThirdComponent
chosen
Indicates that an entity is associated with a specific value of the third (z) component of its isospin in isospin space.
-
D.
hasWeakIsospin
Indicates that an entity possesses a specified value of weak isospin, representing its charge under the weak nuclear interaction.
-
E.
hasIntrinsicParity
Indicates that an entity possesses a specific intrinsic parity value characterizing its behavior under spatial inversion.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 5:22 a.m.