Triple
T173719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communication Theory of Secrecy Systems |
E3531
|
entity |
| Predicate | showsPropertyOf |
P3699
|
FINISHED |
| Object | one-time pad |
—
|
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: one-time pad | Statement: [Communication Theory of Secrecy Systems, showsPropertyOf, one-time pad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsPropertyOf Context triple: [Communication Theory of Secrecy Systems, showsPropertyOf, one-time pad]
-
A.
demonstratedBy
Indicates that something is shown, proven, or made evident through the actions, behavior, or example of a particular entity.
-
B.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
-
C.
displayedWith
Indicates that one entity is shown or presented together alongside another entity in the same context or view.
-
D.
providesProperty
chosen
Indicates that one entity supplies, grants, or makes a particular property or attribute available to another entity.
-
E.
offersViewOf
Indicates that one entity provides a vantage point from which another entity can be seen or visually appreciated.
- 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258e1ec008190a89dd452f72574f4 |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a256689f908190afeb5ee82022a911 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.