Triple
T173725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communication Theory of Secrecy Systems |
E3531
|
entity |
| Predicate | usesModel |
P2006
|
FINISHED |
| Object | noisy communication channel |
—
|
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: noisy communication channel | Statement: [Communication Theory of Secrecy Systems, usesModel, noisy communication channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesModel Context triple: [Communication Theory of Secrecy Systems, usesModel, noisy communication channel]
-
A.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
-
B.
model
chosen
Indicates that one entity serves as a representation, example, or simulation of another entity or concept.
-
C.
designerUsedSelfAsModel
Indicates that the designer served as their own model when creating or showcasing the design.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
usesEquipment
Indicates that an entity employs or operates a particular piece of equipment to perform an action or fulfill a function.
- 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.