Triple
T24081727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauss multiplication formula |
E596521
|
entity |
| Predicate | givesExpressionFor |
P154779
|
FINISHED |
| Object | Γ(nz) |
—
|
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: Γ(nz) | Statement: [Gauss multiplication formula, givesExpressionFor, Γ(nz)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesExpressionFor Context triple: [Gauss multiplication formula, givesExpressionFor, Γ(nz)]
-
A.
hasExpression
Indicates that an entity displays or possesses a particular facial or emotional expression.
-
B.
usesExpressionSystem
Indicates that one entity employs or relies on a particular expression system (e.g., a biological, genetic, or computational framework) to produce, express, or manipulate another entity.
-
C.
coreExpression
Indicates that something is the primary or central expression or representation of another thing.
-
D.
entersExpression
Indicates that one entity moves into, penetrates, or passes through another entity or defined space.
-
E.
hasExpressionIn
Indicates that one entity is manifested, represented, or realized within another entity, typically as a specific form, version, or expression.
- 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_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. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 10:43 p.m.