Triple
T12596999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan’s totient functions |
E300758
|
entity |
| Predicate | valueAtPrime |
P43786
|
FINISHED |
| Object | J_k(p) = p^k - 1 |
—
|
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: J_k(p) = p^k - 1 | Statement: [Jordan’s totient functions, valueAtPrime, J_k(p) = p^k - 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueAtPrime Context triple: [Jordan’s totient functions, valueAtPrime, J_k(p) = p^k - 1]
-
A.
valueAt
chosen
Indicates that one entity specifies the value or content associated with another entity at a particular point, position, or context.
-
B.
value
Indicates that one entity possesses, represents, or corresponds to a particular quantity, quality, or assigned worth.
-
C.
notablePrime
Indicates that a number is a prime with special significance or prominence (for example, due to unique properties, historical importance, or frequent use).
-
D.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
E.
primeCondition
Indicates that a condition or requirement is primary, fundamental, or of highest priority within a given context.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.