Triple
T18426539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XY model |
E450153
|
entity |
| Predicate | spinComponents |
P78112
|
FINISHED |
| Object | two |
—
|
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: two | Statement: [XY model, spinComponents, two]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinComponents Context triple: [XY model, spinComponents, two]
-
A.
nuclearSpin
Indicates that an entity possesses a specific nuclear spin value or nuclear spin state.
-
B.
hasSpinParity
Indicates that a particle or system possesses a specific spin parity value characterizing its combined spin and intrinsic symmetry properties.
-
C.
spinType
Indicates the specific kind or category of spin associated with an entity, such as its spin state, mode, or configuration.
-
D.
chargeConjugationEigenstate
Indicates that a particle or state is an eigenstate of the charge conjugation operator, meaning it transforms into itself up to a definite eigenvalue under charge conjugation.
-
E.
hasSpinMultiplicity
chosen
Indicates that an entity is associated with a specific spin multiplicity value, representing the number of possible spin states in its quantum mechanical description.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51b13ee88819091e7e007d17dcc73 |
completed | April 19, 2026, 6:12 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 11:24 a.m.