Triple
T3780852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulam sequence |
E85412
|
entity |
| Predicate | isStrictlyIncreasing |
P46240
|
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: [Ulam sequence, isStrictlyIncreasing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStrictlyIncreasing Context triple: [Ulam sequence, isStrictlyIncreasing, true]
-
A.
isStrictlyIncreasingFromIndex
chosen
Indicates that a sequence’s values form a strictly increasing order starting from a specified index onward.
-
B.
monotoneIn
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.
-
C.
increasesWith
Indicates that as the value or magnitude of one entity grows, the value or magnitude of another entity correspondingly grows as well.
-
D.
isFastGrowing
Indicates that an entity increases in size, quantity, or impact at a rapid or above-average rate over time.
-
E.
isHigherThan
Indicates that one entity has a greater value, level, or position than another entity.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:12 p.m.