Triple
T25725969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohn–Sham equations |
E645115
|
entity |
| Predicate | solvedWith |
P8791
|
FINISHED |
| Object | real-space grids |
—
|
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: real-space grids | Statement: [Kohn–Sham equations, solvedWith, real-space grids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solvedWith Context triple: [Kohn–Sham equations, solvedWith, real-space grids]
-
A.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
-
B.
solutionDeterminedBy
Indicates that the value or outcome of a solution is fully specified or fixed by the referenced factor(s) or condition(s).
-
C.
providesSolutionFor
Indicates that one entity offers or supplies a remedy, answer, or resolution to a problem, need, or issue associated with another entity.
-
D.
commonlySolvedBy
chosen
Indicates that a problem, task, or issue is typically addressed or resolved through a particular method, tool, or agent.
-
E.
basedOnSolutionOf
Indicates that one entity is derived, developed, or constructed using the solution or outcome produced by another 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcb7bc5c8190b3587f1f4dad9381 |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 11:04 p.m.