Triple
T38635234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Word 2003 |
E937557
|
entity |
| Predicate | usesFileExtensionByDefault |
P5375
|
FINISHED |
| Object | .doc |
—
|
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: .doc | Statement: [Microsoft Word 2003, usesFileExtensionByDefault, .doc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFileExtensionByDefault Context triple: [Microsoft Word 2003, usesFileExtensionByDefault, .doc]
-
A.
includesExtension
Indicates that one entity contains or incorporates another entity as an added or supplementary extension.
-
B.
hasFileExtension
chosen
Indicates that one entity (typically a file) possesses a specific file extension denoting its type or format.
-
C.
introducedFileExtension
Indicates that an entity caused a particular file extension to be created, defined, or brought into use.
-
D.
targetedFileExtensions
Indicates that specific file types, identified by their extensions, are selected or designated as targets for an operation or action.
-
E.
hasExtensionBy
Indicates that one entity is extended, augmented, or further developed by another entity.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.