Triple
T7338279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co2 |
E169184
|
entity |
| Predicate | hasOrderFactorization |
P72933
|
FINISHED |
| Object | 2^18 · 3^6 · 5^3 · 7 · 11 · 23 |
—
|
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: 2^18 · 3^6 · 5^3 · 7 · 11 · 23 | Statement: [Co2, hasOrderFactorization, 2^18 · 3^6 · 5^3 · 7 · 11 · 23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrderFactorization Context triple: [Co2, hasOrderFactorization, 2^18 · 3^6 · 5^3 · 7 · 11 · 23]
-
A.
hasPrimeDecomposition
chosen
Indicates that an entity is associated with the factorization of a number into its constituent prime factors.
-
B.
hasSymmetryGroupOrder
Indicates that an entity possesses a symmetry group whose total number of distinct symmetry operations equals the given order.
-
C.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
D.
agreesWithFactorialOn
Indicates that a function or expression produces the same values as the factorial function for all inputs in a specified domain.
-
E.
hasDenominatorFactor
Indicates that one value appears as a factor in the denominator of another value or expression.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f347f25081908e6086d4073295f5 |
completed | March 27, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c6f028fd748190b2ea5c3081958a42 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:04 p.m.