Triple
T14860109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsch–Jozsa algorithm |
E349464
|
entity |
| Predicate | errorProbability |
P70746
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [Deutsch–Jozsa algorithm, errorProbability, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: errorProbability Context triple: [Deutsch–Jozsa algorithm, errorProbability, 0]
-
A.
hasFailureProbability
chosen
Indicates that an entity is associated with a likelihood or chance that it will fail within a given context or conditions.
-
B.
hasFailureProbabilitySymbol
Indicates that an entity is associated with a symbolic representation of its probability of failure.
-
C.
definesProbability
Indicates that one entity specifies or assigns the probability value associated with another entity or event.
-
D.
hasSuccessProbabilitySymbol
Indicates that an entity is associated with a symbolic representation of its probability of success.
-
E.
riskIfFailure
Indicates that one entity faces potential negative consequences or harm if another entity fails or an attempted action is unsuccessful.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded44598e48190b759a05ed2d9ecaf |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.