Triple
T35508880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BL-5J |
E1026226
|
entity |
| Predicate | usedInOperatingSystemDevices |
P16239
|
FINISHED |
| Object | Symbian |
—
|
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: Symbian | Statement: [BL-5J, usedInOperatingSystemDevices, Symbian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInOperatingSystemDevices Context triple: [BL-5J, usedInOperatingSystemDevices, Symbian]
-
A.
usedByOperatingSystems
chosen
Indicates that something (such as a component, standard, or feature) is utilized or supported by one or more operating systems.
-
B.
usedInDeviceFamily
Indicates that something (such as a component, technology, or feature) is employed or incorporated within a particular family of related devices.
-
C.
systemUsedBy
Indicates that a particular system is utilized or operated by a specified agent or user.
-
D.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
E.
relatedOperatingSystem
Indicates that there is an association between an entity and an operating system that is relevant to its use, compatibility, or operation.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fed09a12648190affcd9bacf7ca275 |
completed | May 9, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69fecf91d6f481908deb60c965c433ed |
completed | May 9, 2026, 6:09 a.m. |
Created at: May 3, 2026, 4:04 p.m.