Triple
T23587237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernoulli distribution |
E582379
|
entity |
| Predicate | expectedValue |
P152810
|
FINISHED |
| Object | p |
—
|
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: p | Statement: [Bernoulli distribution, expectedValue, p]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedValue Context triple: [Bernoulli distribution, expectedValue, p]
-
A.
expectedBenefit
Indicates the benefit or positive outcome that is anticipated to result from a particular action, decision, or relationship between entities.
-
B.
holderExpectation
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
C.
outputExpected
Indicates that a particular output is anticipated or required as the result of a given input, process, or condition.
-
D.
possibleValue
Indicates that a given value is one of the allowed or valid options for a particular attribute, parameter, or variable.
-
E.
expectsEvent
Indicates that one entity anticipates, awaits, or is scheduled to receive the occurrence of a specific event.
- 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_69e248f8d8248190acd5aee77f0d1709 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03195748190b7e34f334902ac93 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:41 p.m.