Triple
T37707050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 9210 Communicator |
E939223
|
entity |
| Predicate | supportsDocumentEditing |
P20985
|
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 9210 Communicator, supportsDocumentEditing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDocumentEditing Context triple: [Nokia 9210 Communicator, supportsDocumentEditing, yes]
-
A.
supportsPageEditing
Indicates that an entity enables or allows editing actions to be performed on a page.
-
B.
supportsEditingType
Indicates that one entity enables or allows another entity to perform or handle a specified type of editing.
-
C.
supportsDocument
chosen
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
-
D.
supportsConcurrentEditing
Indicates that multiple users can edit the same item or resource at the same time without blocking one another.
-
E.
supportsAnonymousEditing
Indicates that the subject allows users to make edits or changes without requiring them to be identified or authenticated.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.