Triple
T26847748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brillouin function |
E675970
|
entity |
| Predicate | isMonotonic |
P10675
|
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, isMonotonic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMonotonic Context triple: [Brillouin function, isMonotonic, true]
-
A.
monotoneIn
chosen
Indicates that the relationship or function preserves a specified order when one of its arguments increases, meaning larger inputs (in that argument) do not lead to smaller outputs with respect to the given ordering.
-
B.
isContinuous
Indicates that a function, process, or relationship changes smoothly without abrupt jumps or breaks over its domain.
-
C.
isStrictlyIncreasingFromIndex
Indicates that a sequence’s values form a strictly increasing order starting from a specified index onward.
-
D.
isDeterministic
Indicates that the outcome of a process or function is fully determined by its inputs, with no randomness or variation between executions.
-
E.
isMonophonic
Indicates that something consists of a single melodic line or voice, without simultaneous independent melodic parts.
- 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_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. |
Created at: April 27, 2026, 5:13 a.m.