Triple
T21494192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermat primality test |
E530310
|
entity |
| Predicate | canUseBase |
P9928
|
FINISHED |
| Object | small fixed bases for some ranges of n |
—
|
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: small fixed bases for some ranges of n | Statement: [Fermat primality test, canUseBase, small fixed bases for some ranges of n]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseBase Context triple: [Fermat primality test, canUseBase, small fixed bases for some ranges of n]
-
A.
usesBase
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
B.
canUse
chosen
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
C.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
D.
usesBaseline
Indicates that one entity relies on or applies another entity as a reference baseline for comparison, measurement, or evaluation.
-
E.
usesBasePoint
Indicates that one entity performs an operation or defines a structure by referencing or relying on a specific base point.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea567244819091863350fedae3ae |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:23 p.m.