Triple
T27824471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navier–Cauchy equations |
E702911
|
entity |
| Predicate | solutionRepresents |
P163387
|
FINISHED |
| Object | displacement field in an elastic body |
—
|
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: displacement field in an elastic body | Statement: [Navier–Cauchy equations, solutionRepresents, displacement field in an elastic body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: solutionRepresents Context triple: [Navier–Cauchy equations, solutionRepresents, displacement field in an elastic body]
-
A.
solutionType
Indicates the specific category or kind of solution associated with an entity or problem.
-
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.
solutionDeterminedBy
Indicates that the value or outcome of a solution is fully specified or fixed by the referenced factor(s) or condition(s).
-
D.
solution
Indicates that one entity is a mixture or substance formed by dissolving another entity (the solute) in a solvent, or more generally a means of solving or resolving a problem involving another entity.
-
E.
solved
Indicates that one entity has successfully found a solution or answer to a problem, task, or challenge involving another entity.
- F. None of above. chosen
Provenance (4 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:50 p.m.