Triple
T24081729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauss multiplication formula |
E596521
|
entity |
| Predicate | usesFactor |
P129262
|
FINISHED |
| Object | n^{nz-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: n^{nz-1/2} | Statement: [Gauss multiplication formula, usesFactor, n^{nz-1/2}]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFactor
Context triple: [Gauss multiplication formula, usesFactor, n^{nz-1/2}]
-
A.
considersFactor
Indicates that one entity takes another entity into account as a factor when forming a judgment, decision, or evaluation.
-
B.
factor
Indicates that one entity is a contributing cause, influence, or component affecting the state, outcome, or existence of another entity.
-
C.
usesDiscountFactor
Indicates that an entity applies a discount factor when evaluating or calculating the value of something over time or across scenarios.
-
D.
usedVia
chosen
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
-
E.
thirdFactor
Indicates that an entity serves as the third factor or element in a multi-factor relationship, typically complementing two other primary factors in a given context.
- 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_69e288c4638c81909bacc28a1e3d436b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dc24b0d081909fcae5e34c6e3b98 |
completed | April 29, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:43 p.m.