Triple
T19433750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubernetes service |
E486181
|
entity |
| Predicate | typicallyProvides |
P65734
|
FINISHED |
| Object | managed control plane |
—
|
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: managed control plane | Statement: [Kubernetes service, typicallyProvides, managed control plane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyProvides Context triple: [Kubernetes service, typicallyProvides, managed control plane]
-
A.
oftenProvides
chosen
Indicates that one entity frequently or regularly supplies, offers, or makes another entity available.
-
B.
providesThat
Indicates that one entity stipulates, specifies, or sets forth a condition, rule, or provision that applies to another entity or situation.
-
C.
providerOf
Indicates that one entity supplies, furnishes, or makes available a good, service, or resource to another entity.
-
D.
aimsToProvide
Indicates that one entity intends or is designed to supply, deliver, or make available something to another entity.
-
E.
mayProvideFor
Indicates that one entity is permitted or has the option to supply, support, or otherwise furnish something for 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.