Triple
T5570691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermat number |
E146191
|
entity |
| Predicate | OEISID |
P43794
|
FINISHED |
| Object | A000215 |
—
|
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: A000215 | Statement: [Fermat number, OEISID, A000215]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: OEISID Context triple: [Fermat number, OEISID, A000215]
-
A.
OEIS
chosen
Indicates that there is a relationship to the On-Line Encyclopedia of Integer Sequences, typically referencing or identifying a specific integer sequence entry.
-
B.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
-
D.
arxivId
Indicates that an entity (such as a paper or work) is associated with a specific arXiv identifier used to reference it in the arXiv repository.
-
E.
identityBasis
Indicates that one entity serves as the defining basis, criterion, or foundation for determining the identity of 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020502a288190af37f9ebb88fccae |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b12826c8190969a584d0f53aa44 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.