Triple
T17558476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle Maximum Availability Architecture |
E427641
|
entity |
| Predicate | includesLayer |
P92765
|
FINISHED |
| Object | database layer |
—
|
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 layer | Statement: [Oracle Maximum Availability Architecture, includesLayer, database layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLayer Context triple: [Oracle Maximum Availability Architecture, includesLayer, database layer]
-
A.
supportsLayerHierarchy
chosen
Indicates that one element can contain and organize other elements within a structured, ordered layer system.
-
B.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
C.
isTypicallyLayered
Indicates that something is usually composed of multiple distinct layers arranged one on top of another.
-
D.
hasLayerFunction
Indicates that one entity serves as the functional role or operational purpose of a specific layer within another entity or system.
-
E.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
- 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_69d889df6dc081908f67dbadc03c07ee |
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.