Triple
T29694251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-duality |
E751298
|
entity |
| Predicate | mapsNeumannBoundaryConditionsTo |
P167613
|
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: [T-duality, mapsNeumannBoundaryConditionsTo, Dirichlet boundary conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapsNeumannBoundaryConditionsTo Context triple: [T-duality, mapsNeumannBoundaryConditionsTo, Dirichlet boundary conditions]
-
A.
boundaryCondition
Indicates the specific constraints or values imposed at the limits or edges of a system, domain, or process that govern its behavior there.
-
B.
boundaryBasis
Indicates that one entity serves as a foundational or defining boundary for another entity.
-
C.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
D.
boundaryMetric
Indicates a relationship where a quantitative measure is assigned to the boundary or interface between entities, capturing some property (such as distance, similarity, or cost) of that boundary.
-
E.
pressureBoundaryComponents
Indicates that certain components serve as boundaries where pressure conditions are defined or applied within a system.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672af46e48190b76e9298e7d23eef |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:19 p.m.