Triple
T27780930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubernetes Custom Resource Definition |
E699333
|
entity |
| Predicate | apiGroup |
P163348
|
FINISHED |
| Object | apiextensions.k8s.io |
—
|
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 | Statement: [Kubernetes Custom Resource Definition, apiGroup, apiextensions.k8s.io]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apiGroup Context triple: [Kubernetes Custom Resource Definition, apiGroup, apiextensions.k8s.io]
-
A.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
B.
routeGroup
Indicates that multiple routes are grouped together as a single logical or organizational unit.
-
C.
groupOrCluster
Indicates that multiple entities are gathered together or associated as a single group or cluster based on some shared relation or proximity.
-
D.
featuresGroup
Indicates that an entity includes or is associated with a specific group as one of its features or components.
-
E.
roleOfGroup
Indicates the function, responsibility, or position that a group holds within a broader context or structure.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:09 p.m.