Triple
T21419968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office core technologies |
E528408
|
entity |
| Predicate | includesComponent |
P1393
|
FINISHED |
| Object | Office document object models |
—
|
NE NERFINISHED |
How this triple was built (3 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: Office document object models | Statement: [Office core technologies, includesComponent, Office document object models]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Office document object models Context triple: [Office core technologies, includesComponent, Office document object models]
-
A.
Multiple Document Interface
Multiple Document Interface is a graphical user interface design that allows a single application window to contain and manage multiple child document windows simultaneously.
-
B.
Microsoft Office binary formats
Microsoft Office binary formats are the legacy proprietary file types (such as .doc, .xls, and .ppt) used by earlier versions of Microsoft Office applications for documents, spreadsheets, and presentations.
-
C.
Office Open XML (ECMA-376)
Office Open XML (ECMA-376) is a standardized, XML-based file format used primarily by Microsoft Office applications for representing word processing documents, spreadsheets, and presentations.
-
D.
OpenDocument format
OpenDocument format is an open, XML-based file format standard for office documents such as text, spreadsheets, and presentations, designed for interoperability across different software suites.
-
E.
Microsoft Office Web Components
Microsoft Office Web Components are a set of browser-based ActiveX controls that allow users to view, analyze, and interact with Office data such as spreadsheets, charts, and pivot tables on web pages.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Office document object models Target entity description: Office document object models are programmable interfaces that allow developers to automate, customize, and manipulate the content and behavior of Microsoft Office documents such as Word, Excel, and PowerPoint files.
-
A.
Multiple Document Interface
Multiple Document Interface is a graphical user interface design that allows a single application window to contain and manage multiple child document windows simultaneously.
-
B.
Microsoft Office binary formats
Microsoft Office binary formats are the legacy proprietary file types (such as .doc, .xls, and .ppt) used by earlier versions of Microsoft Office applications for documents, spreadsheets, and presentations.
-
C.
Office Open XML (ECMA-376)
Office Open XML (ECMA-376) is a standardized, XML-based file format used primarily by Microsoft Office applications for representing word processing documents, spreadsheets, and presentations.
-
D.
OpenDocument format
OpenDocument format is an open, XML-based file format standard for office documents such as text, spreadsheets, and presentations, designed for interoperability across different software suites.
-
E.
Microsoft Office Web Components
Microsoft Office Web Components are a set of browser-based ActiveX controls that allow users to view, analyze, and interact with Office data such as spreadsheets, charts, and pivot tables on web pages.
- F. None of above. chosen
Provenance (2 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2cdb40481909542f2c953bbab64 |
completed | April 22, 2026, 11:36 a.m. |
Created at: April 16, 2026, 5:47 p.m.