Triple
T19434139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oracle Virtual Cloud Network |
E486188
|
entity |
| Predicate | supportsResource |
P15794
|
FINISHED |
| Object | compute instances |
—
|
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: compute instances | Statement: [Oracle Virtual Cloud Network, supportsResource, compute instances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsResource Context triple: [Oracle Virtual Cloud Network, supportsResource, compute instances]
-
A.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
B.
supportsMaterial
Indicates that one entity provides structural or functional support to a material entity, enabling it to be held, stabilized, or borne.
-
C.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
E.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
- 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_69e6335dae10819096e1825741f814ed |
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.