Triple
T31992956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenShift control plane node |
E816917
|
entity |
| Predicate | typicallyDeployedAs |
P4119
|
FINISHED |
| Object | dedicated machine |
—
|
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: dedicated machine | Statement: [OpenShift control plane node, typicallyDeployedAs, dedicated machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyDeployedAs Context triple: [OpenShift control plane node, typicallyDeployedAs, dedicated machine]
-
A.
oftenDeployedIn
Indicates that something is frequently placed, used, or implemented within a particular context, location, or situation.
-
B.
deployedAsPartOf
Indicates that one entity is deployed as a component or subset within the deployment of another entity.
-
C.
typicalDeployment
chosen
Indicates that one entity represents the standard or most commonly used deployment configuration or pattern for the other entity.
-
D.
deployedTo
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
E.
deploymentType
Indicates the manner or configuration in which a system, application, or component is deployed or made operational.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:13 a.m.