Triple
T31992959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OpenShift control plane node |
E816917
|
entity |
| Predicate | usuallyRunsOn |
P11903
|
FINISHED |
| Object | Red Hat Enterprise Linux CoreOS |
—
|
NE NERFINISHED |
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: Red Hat Enterprise Linux CoreOS | Statement: [OpenShift control plane node, usuallyRunsOn, Red Hat Enterprise Linux CoreOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usuallyRunsOn Context triple: [OpenShift control plane node, usuallyRunsOn, Red Hat Enterprise Linux CoreOS]
-
A.
systemOperatesOn
Indicates that a system performs operations, actions, or processing directly on a specified target or resource.
-
B.
runsMostly
Indicates that an entity performs running as its primary or most frequent activity compared to other activities.
-
C.
canRunOn
chosen
Indicates that one entity is capable of operating, executing, or functioning on another entity (such as a platform, system, or environment).
-
D.
operatesPrimarilyOn
Indicates that one entity is mainly or chiefly used to act upon, affect, or process another entity.
-
E.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
- 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_69f6b3badf8481909377856a516a982b |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.