Triple
T21494063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beal conjecture |
E530308
|
entity |
| Predicate | conditionOnVariables |
P79479
|
FINISHED |
| Object | A,B,C,x,y,z are positive integers |
—
|
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,B,C,x,y,z are positive integers | Statement: [Beal conjecture, conditionOnVariables, A,B,C,x,y,z are positive integers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionOnVariables Context triple: [Beal conjecture, conditionOnVariables, A,B,C,x,y,z are positive integers]
-
A.
variableCondition
chosen
Indicates that a variable is subject to a specific state, constraint, or requirement that must hold for a given context or operation.
-
B.
conditionOnCoefficients
Indicates that one entity’s state, validity, or behavior is determined by or contingent upon the values of certain coefficients.
-
C.
containsCondition
Indicates that one entity includes, embodies, or is associated with a particular condition.
-
D.
conditionWhenFound
Indicates the state or circumstances that were present at the time the entity was first discovered or observed.
-
E.
remainderCondition
Indicates that a specified remainder-based condition (such as a modulo constraint) holds between one or more values.
- 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.