Triple
T26756957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wigner 3j symbols |
E674699
|
entity |
| Predicate | hasSelectionRule |
P2846
|
FINISHED |
| Object | m1 plus m2 plus m3 equals zero |
—
|
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: m1 plus m2 plus m3 equals zero | Statement: [Wigner 3j symbols, hasSelectionRule, m1 plus m2 plus m3 equals zero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSelectionRule Context triple: [Wigner 3j symbols, hasSelectionRule, m1 plus m2 plus m3 equals zero]
-
A.
hasRule
chosen
Indicates that an entity is governed, constrained, or defined by a specific rule or set of rules.
-
B.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
C.
hasRuleFor
Indicates that one entity defines or applies a rule that governs or constrains another entity or situation.
-
D.
hasRuleOver
Indicates that one entity holds authority, control, or governance over another entity.
-
E.
hasSelectionStandard
Indicates that there is a defined criterion or set of rules used to choose or filter items, options, or entities.
- 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 3:56 a.m.