Triple
T37946033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 9500 Communicator |
E946607
|
entity |
| Predicate | supportsOfficeApplications |
P86718
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nokia 9500 Communicator, supportsOfficeApplications, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOfficeApplications Context triple: [Nokia 9500 Communicator, supportsOfficeApplications, yes]
-
A.
supportsOffice
Indicates that one entity provides assistance, resources, or endorsement to an office or officeholder in performing its functions or maintaining its operations.
-
B.
appliesToOfficeType
Indicates that something is relevant or applicable specifically to a particular type or category of office.
-
C.
hasOfficeSoftware
chosen
Indicates that an entity possesses, includes, or is equipped with office productivity software.
-
D.
requiresOffice
Indicates that performing or fulfilling the related activity, role, or condition depends on being in or having access to a physical office location.
-
E.
officeIncludes
Indicates that an office contains, encompasses, or has within its scope a specified subordinate space, role, or resource.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.