Triple
T17558586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle Managed Files |
E427643
|
entity |
| Predicate | configuredAt |
P3054
|
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: [Oracle Managed Files, configuredAt, database level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configuredAt Context triple: [Oracle Managed Files, configuredAt, database level]
-
A.
installedAt
chosen
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
B.
partlyConfiguredAs
Indicates that one entity is only partially set up, arranged, or defined to function as another entity or in another role.
-
C.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
D.
oftenConfiguredAs
Indicates that one entity is frequently set up, arranged, or used in the form or role of another entity.
-
E.
configurationVia
Indicates that one entity is set up, customized, or controlled through another entity serving as its configuration mechanism or source.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45624bfe08190991dc088394a5af4 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.