Triple
T19435478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle Database In-Memory |
E486215
|
entity |
| Predicate | storesDataFormat |
P91294
|
FINISHED |
| Object | row format |
—
|
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: row format | Statement: [Oracle Database In-Memory, storesDataFormat, row format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesDataFormat Context triple: [Oracle Database In-Memory, storesDataFormat, row format]
-
A.
storageFormat
chosen
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
B.
storesDataType
Indicates that an entity is designed to hold, manage, or persist information of a specified data type.
-
C.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
D.
storageOption
Indicates how or where something is stored, specifying the chosen method, medium, or configuration for its storage.
-
E.
storageMechanism
Indicates the method or system by which something is stored, preserved, or kept for later use.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6336001488190a05f372779711ed2 |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.