Triple
T7419955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kovalevskaya top |
E171219
|
entity |
| Predicate | hasSolutionMethod |
P4453
|
FINISHED |
| Object | separation of variables |
—
|
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: separation of variables | Statement: [Kovalevskaya top, hasSolutionMethod, separation of variables]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSolutionMethod Context triple: [Kovalevskaya top, hasSolutionMethod, separation of variables]
-
A.
admitsSolution
Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
-
B.
providesSolutionFor
Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with another entity.
-
C.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
-
D.
solutionType
chosen
Indicates the specific category or kind of solution associated with an entity or problem.
-
E.
canBeSolvable
Indicates that a problem, situation, or condition has the potential to be resolved or successfully solved under some circumstances.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ea61248190886e8e55b42ba5f1 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.