Triple
T3780850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulam sequence |
E85412
|
entity |
| Predicate | requiresDistinctSummands |
P51460
|
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, requiresDistinctSummands, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresDistinctSummands Context triple: [Ulam sequence, requiresDistinctSummands, true]
-
A.
isSubtractiveCombination
Indicates that one entity is formed or derived by subtracting one or more components, values, or parts of another entity.
-
B.
isAdditiveFor
Indicates that one entity can be combined with another in a way that their effects or quantities sum together to produce a cumulative result.
-
C.
requiresComplement
Indicates that one entity depends on another entity as a necessary complement to be complete, functional, or valid.
-
D.
hasDistinctSetFor
Indicates that one entity is associated with a separate, non-overlapping collection of items or elements specifically designated for another entity.
-
E.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
- 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_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. |
| PDg | Predicate description generation | batch_69aee633dab88190b14cec8afb19ca6a |
completed | March 9, 2026, 3:24 p.m. |
Created at: March 9, 2026, 3:12 p.m.