Triple
T2555645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transparent Data Encryption |
E56723
|
entity |
| Predicate | isConfiguredAt |
P13644
|
FINISHED |
| Object | database level |
—
|
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: database level | Statement: [Transparent Data Encryption, isConfiguredAt, database level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConfiguredAt Context triple: [Transparent Data Encryption, isConfiguredAt, database level]
-
A.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
isZeroConfiguration
Indicates that something requires no manual setup or configuration to function correctly.
-
C.
hasConfigurationFile
Indicates that an entity is associated with or defined by a specific configuration file.
-
D.
requiresConfiguration
Indicates that one entity depends on another to be set up or configured before it can function or be used.
-
E.
calibratedFor
Indicates that something has been adjusted or tuned to operate accurately or optimally for a specific target, condition, or context.
- 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_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. |
Created at: March 6, 2026, 9:48 p.m.