Triple
T38260702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brenier map |
E1017920
|
entity |
| Predicate | isDefinedBetween |
P190214
|
FINISHED |
| Object | probability measures |
—
|
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: probability measures | Statement: [Brenier map, isDefinedBetween, probability measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefinedBetween Context triple: [Brenier map, isDefinedBetween, probability measures]
-
A.
isIntermediateBetween
Indicates that one entity occupies a position or state that lies between two other entities in a sequence, range, or process.
-
B.
governsBetween
Indicates a governing or regulatory relationship that exists specifically between two entities, often mediating or constraining their interaction.
-
C.
isSeriesBetween
Indicates that one entity forms a series or sequence that spans between two other entities or endpoints.
-
D.
currentBetween
Indicates that the current value of a quantity lies within a specified range between two boundary values.
-
E.
livesBetween
Indicates that one entity resides at a location that is spatially situated between two other reference entities or locations.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc330b4288190858b49d986160706 |
completed | May 7, 2026, 4:52 p.m. |
Created at: May 3, 2026, 4:30 p.m.