Triple
T17385771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bennett–Brassard 1984 protocol |
E422682
|
entity |
| Predicate | eavesdroppingEffect |
P127289
|
FINISHED |
| Object | introduces detectable error rate |
—
|
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: introduces detectable error rate | Statement: [Bennett–Brassard 1984 protocol, eavesdroppingEffect, introduces detectable error rate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eavesdroppingEffect Context triple: [Bennett–Brassard 1984 protocol, eavesdroppingEffect, introduces detectable error rate]
-
A.
canHear
Indicates that one entity is able to perceive sounds produced by another entity.
-
B.
hears
Indicates that one entity perceives or detects sounds produced by another entity or source.
-
C.
echoedIn
Indicates that a sound, statement, or effect produced in one context is repeated, reflected, or resonated in another context.
-
D.
mayHear
Indicates that one entity is permitted or able to hear sounds, speech, or audio produced by another entity.
-
E.
heard
Indicates that one entity perceived a sound produced by another entity or source through hearing.
- 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_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. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:45 a.m.