Triple
T6833560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OEIS A064988 |
E157394
|
entity |
| Predicate | numberBase |
P8195
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [OEIS A064988, numberBase, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberBase Context triple: [OEIS A064988, numberBase, 10]
-
A.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
logarithmBaseDetermines
Indicates that the chosen base of a logarithm determines how a quantity is expressed or scaled in logarithmic terms.
-
C.
number
chosen
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
D.
numeralsRangePerPosition
Indicates the allowed range of numeral values that can appear in each positional place within a number representation.
-
E.
usesPositionalNotation
Indicates that one entity represents numbers using a positional numeral system, where a digit’s value depends on its position.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.