Triple
T30315395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CallKit |
E771042
|
entity |
| Predicate | keyProtocol |
P168838
|
FINISHED |
| Object | CXProviderDelegate |
—
|
NE NERFINISHED |
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: CXProviderDelegate | Statement: [CallKit, keyProtocol, CXProviderDelegate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyProtocol Context triple: [CallKit, keyProtocol, CXProviderDelegate]
-
A.
keyProposal
Indicates that a proposal plays a central or primary role within a broader plan, decision, or set of proposals.
-
B.
keyUse
Indicates that one entity is used as a key or means of access, control, or identification for another entity.
-
C.
keyAgreement
Indicates that two or more parties participate in a cryptographic process to establish a shared secret key for secure communication.
-
D.
keyParameter
Indicates that one entity functions as a primary or critical parameter that significantly influences or determines the behavior, outcome, or configuration of another entity.
-
E.
keyPlan
Indicates that an entity serves as or contains the primary plan, blueprint, or guiding scheme for another entity or process.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6816f2070819084042f987b1be68f |
completed | May 2, 2026, 10:57 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:51 p.m.