Triple
T1523245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euler equations |
E32276
|
entity |
| Predicate | solvedBy |
P8791
|
FINISHED |
| Object | finite volume methods |
—
|
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: finite volume methods | Statement: [Euler equations, solvedBy, finite volume methods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solvedBy Context triple: [Euler equations, solvedBy, finite volume methods]
-
A.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
-
B.
commonlySolvedBy
chosen
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
-
C.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
D.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
-
E.
answeredBy
Indicates that a question, request, or problem is responded to or resolved by a particular entity.
- 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_69a885e9b0ac819093a9806ad0efc82c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93d4756888190bf3872154de11539 |
completed | March 5, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69a907ac7ea081908dd95bb5cc3b9847 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.