Triple
T23446130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D.A. |
E565541
|
entity |
| Predicate | hasSecrecyMethod |
P152314
|
FINISHED |
| Object | enchanted coins communication system |
—
|
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: enchanted coins communication system | Statement: [D.A., hasSecrecyMethod, enchanted coins communication system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecrecyMethod Context triple: [D.A., hasSecrecyMethod, enchanted coins communication system]
-
A.
hasSecrecyPolicy
Indicates that an entity is associated with, governed by, or subject to a specific secrecy or confidentiality policy.
-
B.
hasTypeOfSecrecy
Indicates that something is associated with a particular kind or level of secrecy.
-
C.
hasSecretLevel
Indicates that an entity is associated with a particular secrecy or security classification level.
-
D.
hasSecurityFunction
Indicates that an entity performs, provides, or is responsible for a security-related role, protection mechanism, or safeguarding function for another entity or system.
-
E.
canBeSecret
Indicates that something has the potential or suitability to be kept hidden or confidential from others.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a64939e4819085862e7482e14879 |
completed | April 29, 2026, 6:33 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:51 p.m.