Triple
T25130102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diophantine equations |
E629500
|
entity |
| Predicate | solutionDomain |
P157952
|
FINISHED |
| Object | rational numbers |
—
|
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: rational numbers | Statement: [Diophantine equations, solutionDomain, rational numbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solutionDomain Context triple: [Diophantine equations, solutionDomain, rational numbers]
-
A.
solutionDomain
chosen
Indicates the conceptual or practical area in which a particular problem is addressed or solved.
-
B.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
C.
solution
Indicates that one entity is a mixture or substance formed by dissolving another entity (the solute) in a solvent, or more generally a means of solving or resolving a problem involving another entity.
-
D.
solutionProperty
Indicates that a solution possesses a specific characteristic, attribute, or quality relevant to its behavior, composition, or performance.
-
E.
solutionDeterminedBy
Indicates that the value or outcome of a solution is fully specified or fixed by the referenced factor(s) or condition(s).
- 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_69e2ff3288048190bd82c3b7f7bd0e62 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465f79bd081909a2f5165aa89dc16 |
completed | May 1, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:28 a.m.