Triple
T24916280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OEIS A002850 |
E623992
|
entity |
| Predicate | hasMathematicalDomain |
P127034
|
FINISHED |
| Object | number theory |
—
|
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: number theory | Statement: [OEIS A002850, hasMathematicalDomain, number theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMathematicalDomain Context triple: [OEIS A002850, hasMathematicalDomain, number theory]
-
A.
hasMathematicalProperty
Indicates that one entity possesses or exhibits a specific mathematical property or characteristic.
-
B.
hasMathematicalDiscipline
chosen
Indicates that one entity is associated with or characterized by a particular branch or field of mathematics.
-
C.
mathematicallyDefinedAs
Indicates that one entity is precisely specified or characterized in terms of another using a formal mathematical definition or expression.
-
D.
hasInputDomain
Indicates that a function, process, or operation is defined to accept inputs from a specified set, type, or domain.
-
E.
mathematicallyUses
Indicates that one entity employs or applies another entity within a mathematical context, such as in a formula, proof, computation, or theoretical framework.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 18, 2026, 5:28 a.m.