Triple
T26765600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ξ*− (dss) |
E674927
|
entity |
| Predicate | hasFermionNumber |
P165056
|
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: [Ξ*− (dss), hasFermionNumber, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFermionNumber Context triple: [Ξ*− (dss), hasFermionNumber, 1]
-
A.
hasFermions
Indicates that an entity possesses or is associated with one or more fermionic particles.
-
B.
hasFermionRepresentation
Indicates that one entity can be represented or modeled in terms of fermionic degrees of freedom or a fermionic field theory.
-
C.
hasChiralFermions
Indicates that the subject system or theory includes fermionic particles that exhibit chirality, meaning their left- and right-handed components transform differently under the relevant symmetry group.
-
D.
hasBaryonNumber
Indicates that an entity possesses a specific baryon number, quantifying its net content of baryonic matter (baryons minus antibaryons).
-
E.
fermionOrBoson
Indicates whether an entity is classified as a fermion or a boson according to its quantum statistical behavior.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 27, 2026, 3:59 a.m.