Triple
T20004316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBMutableService |
E494410
|
entity |
| Predicate | usedWithMethod |
P55465
|
FINISHED |
| Object | CBPeripheralManager.add(_:) |
—
|
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: CBPeripheralManager.add(_:) | Statement: [CBMutableService, usedWithMethod, CBPeripheralManager.add(_:)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedWithMethod Context triple: [CBMutableService, usedWithMethod, CBPeripheralManager.add(_:)]
-
A.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
B.
usedInMethod
chosen
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
C.
usesMethods
Indicates that one entity employs, applies, or relies on specific methods or techniques to perform an action or achieve a result.
-
D.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
-
E.
usedVia
Indicates that an entity performs or achieves something by means of, or through the use of, another entity or mechanism.
- 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_69da626b2d748190886981ea90c8b2ea |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e661a3ad148190918f9dce755fe470 |
completed | April 20, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:33 p.m.