Triple
T7939024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | etcd |
E184346
|
entity |
| Predicate | primaryUseInKubernetes |
P19995
|
FINISHED |
| Object | cluster state storage |
—
|
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: cluster state storage | Statement: [etcd, primaryUseInKubernetes, cluster state storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUseInKubernetes Context triple: [etcd, primaryUseInKubernetes, cluster state storage]
-
A.
primaryUseInFeed
Indicates that something is the main or most common way an item is used or presented within a feed.
-
B.
deploymentConcept
Indicates that one entity represents a concept, model, or plan that guides or defines how another entity is deployed or put into operation.
-
C.
usedInClusterConfiguration
chosen
Indicates that something is employed or referenced as part of the setup or parameters of a specific cluster configuration.
-
D.
primaryKernelType
Indicates that one entity is the main or default kernel type associated with another entity.
-
E.
usedInSchedulingSystems
Indicates that something is employed as a component or mechanism within scheduling systems to plan, allocate, or manage tasks, resources, or time.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3af0a2048190838d1aeda59fda0b |
completed | March 31, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:08 p.m.