Triple
T7938948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kube-controller-manager |
E184345
|
entity |
| Predicate | runsControllers |
P7944
|
FINISHED |
| Object | Node controller |
—
|
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: Node controller | Statement: [kube-controller-manager, runsControllers, Node controller]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsControllers Context triple: [kube-controller-manager, runsControllers, Node controller]
-
A.
runsFrom
Indicates that one entity flees or escapes away from another entity.
-
B.
runsUnder
Indicates that one process, task, or component operates within the control, environment, or context provided by another system, platform, or framework.
-
C.
runBy
chosen
Indicates that an entity is operated, managed, or controlled by another entity.
-
D.
bundledController
Indicates that one controller is packaged or grouped together with another controller as part of the same bundle or unit.
-
E.
runs
Indicates that an entity moves swiftly on foot, typically using its legs in a continuous, rapid motion.
- 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.