Triple
T27594391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contour |
E699854
|
entity |
| Predicate | deploysAs |
P85293
|
FINISHED |
| Object | Kubernetes DaemonSet (Envoy data plane) |
—
|
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: Kubernetes DaemonSet (Envoy data plane) | Statement: [Contour, deploysAs, Kubernetes DaemonSet (Envoy data plane)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deploysAs Context triple: [Contour, deploysAs, Kubernetes DaemonSet (Envoy data plane)]
-
A.
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.
-
B.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
C.
canDeployAs
chosen
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
D.
deployer
Indicates the agent or entity that carries out the deployment of a system, resource, or artifact.
-
E.
deployerType
Indicates the role or category of the agent responsible for deploying or initiating the associated entity or action.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:06 p.m.