Triple
T7938946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kube-controller-manager |
E184345
|
entity |
| Predicate | leaderElectionResource |
P79906
|
FINISHED |
| Object | ConfigMap |
—
|
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: ConfigMap | Statement: [kube-controller-manager, leaderElectionResource, ConfigMap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderElectionResource Context triple: [kube-controller-manager, leaderElectionResource, ConfigMap]
-
A.
selectionOfLeader
Indicates the process or act by which one entity is chosen or designated as the leader among a group of entities.
-
B.
leaderSince
Indicates that an entity has held a leadership role over another entity starting from a specified point in time.
-
C.
targetLeader
Indicates that one entity is the primary leader, focal authority, or main decision-maker targeted or referenced by another entity or action.
-
D.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
E.
leaderIsUsually
Indicates that an entity typically serves as the leader in relation to another entity or within a given context.
- 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_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. |
| PDg | Predicate description generation | batch_69caf7882b048190baa333af9f698590 |
completed | March 30, 2026, 10:22 p.m. |
Created at: March 30, 2026, 5:08 p.m.