Triple
T2555614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transparent Data Encryption |
E56723
|
entity |
| Predicate | isTransparentTo |
P40821
|
FINISHED |
| Object | applications |
—
|
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: applications | Statement: [Transparent Data Encryption, isTransparentTo, applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTransparentTo Context triple: [Transparent Data Encryption, isTransparentTo, applications]
-
A.
hasTransparencyRequirement
Indicates that one entity is obligated to provide clear, accessible information or disclosure to another entity or to the public.
-
B.
isPassedThroughBy
Indicates that something serves as a medium, route, or channel through which another thing moves, flows, or is transmitted.
-
C.
transparency
Indicates that an entity’s internal processes, information, or decision-making are openly accessible and understandable to others.
-
D.
isSeeOf
Indicates that one entity serves as the episcopal or ecclesiastical seat (see) of another, typically a bishop or similar religious office.
-
E.
obscuredIn
Indicates that one entity is hidden, blocked, or made less visible due to the presence or influence of another entity.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd5a1cd508190a660b9a3c6b7cbcb |
completed | March 7, 2026, 7:37 a.m. |
Created at: March 6, 2026, 9:48 p.m.