Triple
T25602504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GF(p) |
E641824
|
entity |
| Predicate | additionOperation |
P819
|
FINISHED |
| Object | addition modulo p |
—
|
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: addition modulo p | Statement: [GF(p), additionOperation, addition modulo p]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: additionOperation Context triple: [GF(p), additionOperation, addition modulo p]
-
A.
typeOfOperation
chosen
Indicates the specific kind or category of operation being performed or referenced in a given context.
-
B.
isAdditiveFor
Indicates that one entity can be combined with another in a way that their effects or quantities sum together to produce a cumulative result.
-
C.
arithmetic
Indicates a relationship where one entity performs or represents a mathematical operation (such as addition, subtraction, multiplication, or division) involving one or more other entities.
-
D.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
E.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a7d7d881909014fdf3746f981b |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:36 p.m.