Triple
T23587229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bernoulli distribution |
E582379
|
entity |
| Predicate | typicalOutcomeLabel |
P22603
|
FINISHED |
| Object | success |
—
|
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: success | Statement: [Bernoulli distribution, typicalOutcomeLabel, success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOutcomeLabel Context triple: [Bernoulli distribution, typicalOutcomeLabel, success]
-
A.
outcomeType
chosen
Indicates the specific category or nature of the result produced by an event, process, or action.
-
B.
typicalConclusion
Indicates that one entity is the usual or expected outcome, result, or ending that follows from another entity or situation.
-
C.
describesOutcomeOf
Indicates that one entity specifies or characterizes the result, consequence, or outcome produced by another entity or process.
-
D.
initialOutcome
Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
-
E.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
- F. None of above.
Provenance (3 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. |
Created at: April 17, 2026, 6:41 p.m.