Triple
T5101008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CoreBluetooth |
E114979
|
entity |
| Predicate | usesPattern |
P12995
|
FINISHED |
| Object | delegate-based callbacks |
—
|
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: delegate-based callbacks | Statement: [CoreBluetooth, usesPattern, delegate-based callbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPattern Context triple: [CoreBluetooth, usesPattern, delegate-based callbacks]
-
A.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
B.
usagePattern
chosen
Indicates how something is typically used or the recurring manner in which it is employed or consumed.
-
C.
supportsPatternType
Indicates that one entity is compatible with, or capable of handling, a specified pattern type.
-
D.
usesMatchesFrom
Indicates that one entity relies on or incorporates matches (e.g., pattern matches, rule matches, or result matches) produced by another entity or process.
-
E.
patroonOf
Indicates a relationship in which one entity acts as a patron, sponsor, or protector providing support or resources to 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd758381dc8190ac491788d27ab8e0 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.