Triple
T30315951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Design Awards 2010 |
E771054
|
entity |
| Predicate | focusPlatform |
P175981
|
FINISHED |
| Object | iOS |
—
|
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: iOS | Statement: [Apple Design Awards 2010, focusPlatform, iOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusPlatform Context triple: [Apple Design Awards 2010, focusPlatform, iOS]
-
A.
focusesOnPlatform
chosen
Indicates that an entity’s attention, effort, or activity is primarily directed toward a particular platform as its main context or target.
-
B.
focusFeature
Indicates that one entity is the primary or emphasized feature, aspect, or attribute being highlighted or concentrated on in relation to another.
-
C.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
D.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
E.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
- 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_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 29, 2026, 7:51 p.m.