Triple
T15977091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cauchy functional equation |
E387476
|
entity |
| Predicate | generalCodomain |
P7031
|
FINISHED |
| Object | abelian group |
—
|
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: abelian group | Statement: [Cauchy functional equation, generalCodomain, abelian group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generalCodomain Context triple: [Cauchy functional equation, generalCodomain, abelian group]
-
A.
codomain
chosen
Indicates the set of all possible output values that a function or mapping can produce, regardless of which values are actually attained.
-
B.
outputDomain
Indicates the type or range of values that can be produced as the result of a function, process, or system.
-
C.
coordinateDomain
Indicates that two or more entities share the same coordinate system or spatial reference framework for describing positions.
-
D.
domainOfInterpretation
Indicates that the specified set constitutes the universe of discourse over which all variables and quantifiers in a logical system are interpreted.
-
E.
domainOfVariables
Indicates that the predicate specifies the set or type of values that the variables involved in an expression or formula are allowed to take.
- 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_69d86da94ccc819083d187f5dc6a123e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d9d8e881909b559a3e3ca21d24 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:54 a.m.