Triple
T6293600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernoulli trials |
E141077
|
entity |
| Predicate | hasFailureProbabilitySymbol |
P70745
|
FINISHED |
| Object | q |
—
|
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: q | Statement: [Bernoulli trials, hasFailureProbabilitySymbol, q]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFailureProbabilitySymbol Context triple: [Bernoulli trials, hasFailureProbabilitySymbol, q]
-
A.
hasStandardDeviationSymbol
Indicates that a given notation, variable, or symbol is used to represent the standard deviation in a statistical context.
-
B.
hasVarianceSymbol
Indicates that one entity is associated with, or represented by, a specific variance symbol in a mathematical or statistical context.
-
C.
hasSymbolicForm
Indicates that one entity serves as the symbolic representation or abstract form of another entity.
-
D.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
E.
definesProbability
Indicates that one entity specifies or assigns the probability value associated with another entity or 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_69c008cdf2ac8190bb640c94478fb4ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06438654481908c9833c5f0d61773 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c06284848c8190a0151ff3e8682889 |
completed | March 22, 2026, 9:43 p.m. |
Created at: March 22, 2026, 4:27 p.m.