Triple
T33203894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTKView |
E849972
|
entity |
| Predicate | renderLoopMode |
P105517
|
FINISHED |
| Object | displayLink-driven |
—
|
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: displayLink-driven | Statement: [MTKView, renderLoopMode, displayLink-driven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renderLoopMode Context triple: [MTKView, renderLoopMode, displayLink-driven]
-
A.
renderingMode
Indicates the specific way in which content or graphics are processed and displayed (e.g., style, technique, or pipeline used for rendering).
-
B.
hasLoopMode
chosen
Indicates that an entity operates or is configured in a mode where its behavior or process repeats in a loop.
-
C.
displayMode
Indicates how content or information is visually presented or arranged to the user.
-
D.
loopModeDescription
Indicates the descriptive text explaining the current loop mode or looping behavior setting.
-
E.
loopType
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
- 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.