Triple
T17385802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BB84 quantum key distribution protocol |
E422683
|
entity |
| Predicate | usesBasis |
P79686
|
FINISHED |
| Object | computational basis |
—
|
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: computational basis | Statement: [BB84 quantum key distribution protocol, usesBasis, computational basis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesBasis Context triple: [BB84 quantum key distribution protocol, usesBasis, computational basis]
-
A.
usedAsBasisFor
Indicates that one entity serves as the foundation, reference, or starting point upon which another entity is developed, derived, justified, or constructed.
-
B.
usesBase
chosen
Indicates that one entity relies on or operates using another entity as its foundational resource, framework, or reference point.
-
C.
usesBaseline
Indicates that one entity relies on or applies another entity as a reference baseline for comparison, measurement, or evaluation.
-
D.
hasBasisIn
Indicates that one entity is founded, derived, or justified on the grounds of another entity.
-
E.
isBasedOn
Indicates that one entity is derived from, inspired by, or developed using the content, structure, or principles of another entity.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a89c5008190a277a68e5cfe67b7 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.