Triple
T2568017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Mobile |
E57595
|
entity |
| Predicate | focusAfter2015 |
P37801
|
FINISHED |
| Object | low-end and mid-range smartphones |
—
|
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: low-end and mid-range smartphones | Statement: [Microsoft Mobile, focusAfter2015, low-end and mid-range smartphones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusAfter2015 Context triple: [Microsoft Mobile, focusAfter2015, low-end and mid-range smartphones]
-
A.
formerFocus
Indicates that an entity previously served as the primary focus or main subject of attention, but no longer holds that status.
-
B.
focusesOnYears
Indicates that something is primarily concerned with or directed toward specific years or time periods.
-
C.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
D.
focusAfterTransition
chosen
Indicates that focus is moved to a specific element or area after a transition or state change has completed.
-
E.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd36191848190b6255fa9029429bd |
completed | March 7, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.