Triple
T7277771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gluon |
E163072
|
entity |
| Predicate | hasSpinParity |
P76189
|
FINISHED |
| Object | 1- |
—
|
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- | Statement: [gluon, hasSpinParity, 1-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpinParity Context triple: [gluon, hasSpinParity, 1-]
-
A.
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.
-
B.
hasSpin
Indicates that one entity possesses or exhibits rotational motion or angular momentum.
-
C.
hasTypicalSpinState
Indicates the usual or characteristic spin quantum state that an entity (such as a particle or system) most commonly exhibits under normal conditions.
-
D.
hasIsospin
Indicates that one particle possesses a specific isospin value or quantum number in relation to another reference or classification framework.
-
E.
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.
- 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 2:59 p.m.