Triple
T26847749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brillouin function |
E675970
|
entity |
| Predicate | isOddFunction |
P161531
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Brillouin function, isOddFunction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOddFunction Context triple: [Brillouin function, isOddFunction, true]
-
A.
isOdd
Indicates that a given number has a remainder of 1 when divided by 2, i.e., it is not evenly divisible by 2.
-
B.
isEvenOrOdd
Indicates that an entity is classified as either even or odd with respect to a numerical parity property.
-
C.
evenFunction
Indicates that a function is even, meaning its output is unchanged when the input’s sign is reversed (f(x) = f(−x) for all x in its domain).
-
D.
evennessProperty
Indicates that a quantity, value, or count has the property of being even, typically divisible into two equal integer parts without remainder.
-
E.
isEvenUnimodular
Indicates that a lattice is both even (all vector norms are even integers) and unimodular (has determinant ±1, i.e., is self-dual).
- 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_69eee9b8d5e88190a07d3455c0fbb21f |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b8f2dc081908c3f0a1597569328 |
completed | May 2, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6142a0b988190b404d078f73c3cb9 |
completed | May 2, 2026, 3:11 p.m. |
Created at: April 27, 2026, 5:13 a.m.