Triple
T32516881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twisted Edwards curve |
E831082
|
entity |
| Predicate | requiresConditionOnParameter |
P198759
|
FINISHED |
| Object | a ≠ 0 |
—
|
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: a ≠ 0 | Statement: [Twisted Edwards curve, requiresConditionOnParameter, a ≠ 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresConditionOnParameter Context triple: [Twisted Edwards curve, requiresConditionOnParameter, a ≠ 0]
-
A.
requiresScaleParameterCondition
Indicates that the use or validity of something is contingent on the presence or specification of a scale parameter.
-
B.
hasCondition
Indicates that an entity possesses, experiences, or is affected by a particular condition or state.
-
C.
modificationCondition
Indicates the specific circumstances or requirements under which a change or modification to something is permitted, triggered, or becomes applicable.
-
D.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
E.
conditionWhenFound
Indicates the state or circumstances that were present at the time the entity was first discovered or observed.
- F. None of above. chosen
Provenance (4 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
| PDg | Predicate description generation | batch_69ff04901ab081908b68563836fcdc99 |
completed | May 9, 2026, 9:55 a.m. |
Created at: May 1, 2026, 1 a.m.