Triple
T23423279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office 2007 |
E560722
|
entity |
| Predicate | introducedFileExtension |
P152226
|
FINISHED |
| Object | .docx |
—
|
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: .docx | Statement: [Microsoft Office 2007, introducedFileExtension, .docx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedFileExtension Context triple: [Microsoft Office 2007, introducedFileExtension, .docx]
-
A.
formerExtension
Indicates that one entity previously served as an extension or subsidiary part of another entity, but no longer holds that status.
-
B.
definesExtension
Indicates that one entity specifies or establishes the extension, scope, or detailed form of another entity.
-
C.
includesExtension
Indicates that one entity contains or incorporates another entity as an added or supplementary extension.
-
D.
extensionOpenedWith
Indicates that a file extension is opened or handled using a particular application or tool.
-
E.
extensionType
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54780d88190a7d5c1426b85b7fc |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:47 p.m.