Triple
T22666373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poisson equation |
E559802
|
entity |
| Predicate | commonBoundaryConditions |
P25792
|
FINISHED |
| Object | Dirichlet boundary conditions |
—
|
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: Dirichlet boundary conditions | Statement: [Poisson equation, commonBoundaryConditions, Dirichlet boundary conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonBoundaryConditions Context triple: [Poisson equation, commonBoundaryConditions, Dirichlet boundary conditions]
-
A.
boundaryCondition
chosen
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
-
B.
typicalBoundary
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
C.
boundaryBasis
Indicates that one entity serves as a foundational or defining boundary for another entity.
-
D.
boundaryTheory
Indicates that one entity serves as a theoretical or conceptual boundary or limit for another entity within a given framework or domain.
-
E.
formsBoundaryType
Indicates that one entity serves as a specific type of boundary for 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781c2c808190baf6964ca1eced6f |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:09 p.m.