Triple
T9843603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cauchy–Riemann equations |
E239285
|
entity |
| Predicate | imaginaryPartNotation |
P72939
|
FINISHED |
| Object | v(x,y) |
—
|
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: v(x,y) | Statement: [Cauchy–Riemann equations, imaginaryPartNotation, v(x,y)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imaginaryPartNotation Context triple: [Cauchy–Riemann equations, imaginaryPartNotation, v(x,y)]
-
A.
imaginaryPart
chosen
Indicates the relationship that maps a complex-valued entity to the value of its imaginary component.
-
B.
isImaginary
Indicates that something exists only in the mind or imagination and does not have a corresponding real-world or physical existence.
-
C.
isPurelyImaginary
Indicates that the entity exists only in imagination or theory and has no real or physical existence.
-
D.
offsetNotation
Indicates that one representation specifies how far and in what way another representation is shifted or displaced from a reference point or baseline.
-
E.
symbolInComplexAnalysis
Indicates that a given symbol is used specifically within the context or notation of complex analysis.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35c8e348190aa090c71bf6f30eb |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.