Triple
T27780931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubernetes Custom Resource Definition |
E699333
|
entity |
| Predicate | apiVersion |
P15694
|
FINISHED |
| Object | apiextensions.k8s.io/v1 |
—
|
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: apiextensions.k8s.io/v1 | Statement: [Kubernetes Custom Resource Definition, apiVersion, apiextensions.k8s.io/v1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apiVersion Context triple: [Kubernetes Custom Resource Definition, apiVersion, apiextensions.k8s.io/v1]
-
A.
protocolVersion
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
B.
APIType
chosen
Indicates the type or category of an API associated with or used by an entity.
-
C.
versionOf
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
D.
APIName
Indicates the specific name or identifier assigned to an application programming interface (API) used to distinguish it from other APIs.
-
E.
exportVersionOf
Indicates that one entity is a version of another specifically created or designated for export (e.g., for external distribution or use).
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637ce6b688190813ef657673cb88d |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:09 p.m.