Triple
T2126380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schwarzschild–Milne equations |
E46433
|
entity |
| Predicate | solutionMethods |
P8791
|
FINISHED |
| Object | discrete ordinates 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: discrete ordinates methods | Statement: [Schwarzschild–Milne equations, solutionMethods, discrete ordinates methods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solutionMethods Context triple: [Schwarzschild–Milne equations, solutionMethods, discrete ordinates methods]
-
A.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
B.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
-
C.
resolutionMethod
Indicates the specific approach, technique, or process used to resolve a problem, conflict, or issue.
-
D.
commonlySolvedBy
chosen
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
-
E.
isSolutionOf
Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbb59182081908470f9be97e272c8 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bd86cc8190938ef06c1ed6d969 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.