Triple
T38260740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenier map |
E1017920
|
entity |
| Predicate | hasRegularityDependingOn |
—
|
GENERATED |
| Object | regularity of source and target densities |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularityDependingOn Context triple: [Brenier map, hasRegularityDependingOn, regularity of source and target densities]
-
A.
hasRegularity
Indicates that one entity exhibits a consistent, recurring pattern or uniform behavior with respect to another entity or over time.
-
B.
regularityAssumption
chosen
Indicates that a relationship or process is assumed to behave in a consistent, well-behaved manner (e.g., continuity, smoothness, or stability) so that certain analyses or inferences are valid.
-
C.
areRegularIn
Indicates that entities participate in or occur within a context, pattern, or structure in a consistent, uniform, and rule-governed manner.
-
D.
regulatesOrIsRegulatedBy
Indicates a bidirectional regulatory relationship in which one entity controls, influences, or modulates another, or is itself controlled, influenced, or modulated by that other entity.
-
E.
oftenDeterministicDuring
Indicates that one entity tends to behave or occur in a predictable, rule-governed way during the time, process, or condition specified by another entity.
- F. None of above.
Provenance (1 batch)
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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:30 p.m.