Triple
T31993051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenShift Machine Config Operator |
E816919
|
entity |
| Predicate | appliesConfigurationTo |
P1129
|
FINISHED |
| Object | control plane nodes |
—
|
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: control plane nodes | Statement: [OpenShift Machine Config Operator, appliesConfigurationTo, control plane nodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesConfigurationTo Context triple: [OpenShift Machine Config Operator, appliesConfigurationTo, control plane nodes]
-
A.
appliesToConfiguration
Indicates that something (such as a rule, setting, or operation) is relevant to, affects, or is intended for a particular configuration.
-
B.
exportConfigurationFor
Indicates that one entity produces and outputs a configuration suitable for use by another specified entity.
-
C.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
D.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
E.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
- 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_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 1, 2026, 12:13 a.m.