Triple
T20004223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBDescriptor |
E494408
|
entity |
| Predicate | callbackMethod |
P108442
|
FINISHED |
| Object | peripheral(_:didUpdateValueFor:error:) |
—
|
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: peripheral(_:didUpdateValueFor:error:) | Statement: [CBDescriptor, callbackMethod, peripheral(_:didUpdateValueFor:error:)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callbackMethod Context triple: [CBDescriptor, callbackMethod, peripheral(_:didUpdateValueFor:error:)]
-
A.
bindingMethod
Indicates the technique or process by which two or more entities are joined, attached, or held together.
-
B.
calledBackBy
chosen
Indicates that one entity returns a previous call or contact initiated by another entity.
-
C.
calledEvent
Indicates that an entity initiated or made a phone call to another entity during a specific event or time.
-
D.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
E.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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.