Triple

T7938843
Position Surface form Disambiguated ID Type / Status
Subject kube-apiserver E184343 entity
Predicate usesAdmissionControl P53898 FINISHED
Object admission plugins 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: admission plugins | Statement: [kube-apiserver, usesAdmissionControl, admission plugins]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesAdmissionControl
Context triple: [kube-apiserver, usesAdmissionControl, admission plugins]
  • A. controlsAdmissionsFor chosen
    Indicates that one entity has authority or responsibility over managing and deciding admissions for another entity.
  • B. hasAdmission
    Indicates that an entity possesses or is associated with a specific admission event, record, or status (such as being admitted to a place, program, or institution).
  • C. admissionPolicy
    Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
  • D. admissionSource
    Indicates the origin or point of referral from which an entity (typically a person or case) was admitted into a system, institution, or process.
  • E. canEnforce
    Indicates that one entity has the authority or capability to compel compliance with rules, decisions, or obligations upon 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_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.