Triple
T23423306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office 2007 |
E560722
|
entity |
| Predicate | fileFormatCompatibility |
P91197
|
FINISHED |
| Object | backward compatibility with binary Office formats via converters |
—
|
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: backward compatibility with binary Office formats via converters | Statement: [Microsoft Office 2007, fileFormatCompatibility, backward compatibility with binary Office formats via converters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fileFormatCompatibility Context triple: [Microsoft Office 2007, fileFormatCompatibility, backward compatibility with binary Office formats via converters]
-
A.
fileFormatStandard
Indicates that something conforms to, specifies, or defines a standardized structure and rules for how data is organized and stored in a file.
-
B.
formatCompatibleWith
chosen
Indicates that one format can be correctly used, interpreted, or processed in conjunction with another format without conflict or loss of information.
-
C.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
D.
typicalFileFormat
Indicates the usual or standard file format typically associated with or used for a given entity or context.
-
E.
preservationFormat
Indicates the format or encoding in which something is maintained specifically for long-term preservation.
- 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_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. |
Created at: April 17, 2026, 5:47 p.m.