Triple
T27780937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubernetes Custom Resource Definition |
E699333
|
entity |
| Predicate | specField |
P33246
|
FINISHED |
| Object | names |
—
|
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: names | Statement: [Kubernetes Custom Resource Definition, specField, names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specField Context triple: [Kubernetes Custom Resource Definition, specField, names]
-
A.
specType
Indicates the specific type or category of a specification that an entity is associated with.
-
B.
fieldAdvanced
Indicates that a particular field or attribute has progressed beyond a basic or standard level, reflecting a more complex, specialized, or developed state.
-
C.
definesField
chosen
Indicates that one entity specifies or declares a particular field or attribute that belongs to or characterizes another entity.
-
D.
possibleField
Indicates that an entity may be associated with, or located within, a particular field or domain, but this association is not certain or exclusive.
-
E.
fieldComponent
Indicates that one entity functions as a constituent or sub-part within a larger field or domain defined by 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_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 5:09 p.m.