Triple
T37659677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenovo Symbian smartphones |
E937687
|
entity |
| Predicate | mobilePlatformGeneration |
P81855
|
FINISHED |
| Object | pre-Android era |
—
|
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: pre-Android era | Statement: [Lenovo Symbian smartphones, mobilePlatformGeneration, pre-Android era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobilePlatformGeneration Context triple: [Lenovo Symbian smartphones, mobilePlatformGeneration, pre-Android era]
-
A.
targetDeviceGeneration
Indicates the specific hardware or model generation of the device that is the focus or recipient of an action or relationship.
-
B.
videoGamePlatformGeneration
Indicates that a video game platform belongs to, or is classified within, a particular generation of video game hardware or consoles.
-
C.
targetPlatformGeneration
chosen
Indicates the generation or version of the platform that an action, resource, or entity is specifically intended to run on or be compatible with.
-
D.
mobileReleaseYear
Indicates the calendar year in which a mobile device or mobile application was released.
-
E.
originalPlatformGeneration
Indicates that one platform is the initial or first-generation version from which another platform or subsequent generations are derived.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.