Triple
T33204112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTKViewDelegate |
E849978
|
entity |
| Predicate | callbackTiming |
P163165
|
FINISHED |
| Object | called each frame when MTKView needs to render |
—
|
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: called each frame when MTKView needs to render | Statement: [MTKViewDelegate, callbackTiming, called each frame when MTKView needs to render]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: callbackTiming Context triple: [MTKViewDelegate, callbackTiming, called each frame when MTKView needs to render]
-
A.
requiresTiming
Indicates that one entity’s occurrence, execution, or validity depends on being coordinated with a specific time or temporal condition related to another entity.
-
B.
timingParameter
Indicates a relationship where one entity specifies or controls a temporal setting, constraint, or configuration parameter that determines the timing behavior of another entity or process.
-
C.
reviewTiming
Indicates the point in time or period relative to an event or process when a review is conducted.
-
D.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
-
E.
callbackType
chosen
Indicates the specific kind or category of callback event or function associated with an entity or interaction.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.