Triple
T14860120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsch–Jozsa algorithm |
E349464
|
entity |
| Predicate | numberOfQubitsRequired |
P115905
|
FINISHED |
| Object | n+1 |
—
|
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: n+1 | Statement: [Deutsch–Jozsa algorithm, numberOfQubitsRequired, n+1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfQubitsRequired Context triple: [Deutsch–Jozsa algorithm, numberOfQubitsRequired, n+1]
-
A.
minimumCircuitsRequired
Indicates the smallest number of circuits that must be present or used for a given system, configuration, or requirement to be satisfied.
-
B.
requiredNumberOfStates
Indicates the specific number of distinct states that something must have or support in order to meet a given requirement or condition.
-
C.
isQuantumOf
Indicates that one entity represents a discrete, indivisible unit or packet of the other entity in a quantized relationship.
-
D.
computationalCost
Indicates the amount of computing resources (such as time, memory, or processing power) required to perform a given operation or process.
-
E.
numberOfQueries
Indicates the total count of queries associated with or performed in a given context or entity.
- 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_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. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.