Triple
T21494363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carmichael number |
E530314
|
entity |
| Predicate | smallestElement |
P64837
|
FINISHED |
| Object | 561 |
—
|
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: 561 | Statement: [Carmichael number, smallestElement, 561]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: smallestElement Context triple: [Carmichael number, smallestElement, 561]
-
A.
isSmallestOf
chosen
Indicates that an entity has the minimum size or value within a specified set or group of entities.
-
B.
minimumNumber
Indicates that the associated value is the smallest or least quantity allowed, required, or observed within a given set or context.
-
C.
minimumDenomination
Indicates that one entity specifies the smallest allowable unit or value (minimum denomination) in which another entity can be expressed, transacted, or divided.
-
D.
minimumRange
Indicates the smallest allowable or observed value within a specified range for a given relationship or measurement.
-
E.
minimumSize
Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea567244819091863350fedae3ae |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.