Triple
T38635239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Word 2003 |
E937557
|
entity |
| Predicate | supportsPageSetup |
P206592
|
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: [Microsoft Word 2003, supportsPageSetup, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPageSetup Context triple: [Microsoft Word 2003, supportsPageSetup, yes]
-
A.
printingSupport
Indicates that one entity provides or is compatible with printing capabilities or services for another entity.
-
B.
supportsPageFlipping
Indicates that one entity provides the capability for another entity to flip between pages, such as in a document or paginated interface.
-
C.
supportsPageEditing
Indicates that an entity enables or allows editing actions to be performed on a page.
-
D.
hasPrintFeature
Indicates that an entity possesses a specific printing-related characteristic or capability.
-
E.
supportsBannerPages
Indicates that one entity provides the capability to display or handle banner-style pages for another entity.
- F. None of above. chosen
Provenance (4 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.