Triple
T30315291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iOS 10 |
E771040
|
entity |
| Predicate | includedFramework |
P200603
|
FINISHED |
| Object | SiriKit |
—
|
NE NERFINISHED |
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: SiriKit | Statement: [iOS 10, includedFramework, SiriKit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedFramework Context triple: [iOS 10, includedFramework, SiriKit]
-
A.
isPartOfFramework
Indicates that one entity functions as a component, module, or element within a larger structured framework or system.
-
B.
appliesFramework
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
-
C.
parentFramework
Indicates that one framework serves as the higher-level or containing framework from which another framework is derived, organized, or structured.
-
D.
relatesToFramework
chosen
Indicates a general association or connection between an entity and a particular framework (such as a software, legal, or conceptual framework).
-
E.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
Created at: April 29, 2026, 7:51 p.m.