Triple
T27780945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubernetes Custom Resource Definition |
E699333
|
entity |
| Predicate | namesField |
P163561
|
FINISHED |
| Object | shortNames |
—
|
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: shortNames | Statement: [Kubernetes Custom Resource Definition, namesField, shortNames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namesField Context triple: [Kubernetes Custom Resource Definition, namesField, shortNames]
-
A.
namesField
chosen
Indicates that one entity serves as the name or label assigned to a particular field of another entity.
-
B.
namesakeField
Indicates that one entity serves as the namesake for a particular field, such that the field is named after that entity.
-
C.
namedPersonField
Indicates that a particular data field is designated to contain a person’s name.
-
D.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
E.
namesAs
Indicates that one entity assigns or uses a particular name or label to refer to 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 5:10 p.m.