Triple
T9843912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cauchy–Euler equation |
E239291
|
entity |
| Predicate | hasStandardSolutionMethod |
P4453
|
FINISHED |
| Object | power-law ansatz y = x^m |
—
|
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: power-law ansatz y = x^m | Statement: [Cauchy–Euler equation, hasStandardSolutionMethod, power-law ansatz y = x^m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardSolutionMethod Context triple: [Cauchy–Euler equation, hasStandardSolutionMethod, power-law ansatz y = x^m]
-
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.
hasStandardImplementation
Indicates that an entity has a defined, commonly accepted implementation that follows an established standard or specification.
-
E.
solutionType
chosen
Indicates the specific category or kind of solution associated with an entity or problem.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35dc29c819080203be5b904dc9d |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.