Triple
T38635273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Excel 2003 |
E937558
|
entity |
| Predicate | supportsDataImport |
P60286
|
FINISHED |
| Object | text files |
—
|
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: text files | Statement: [Microsoft Excel 2003, supportsDataImport, text files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDataImport Context triple: [Microsoft Excel 2003, supportsDataImport, text files]
-
A.
supportsImportExport
chosen
Indicates that one entity provides functionality for importing and exporting data or resources to and from another entity.
-
B.
supportsDataFrom
Indicates that one entity provides, validates, or underpins the data used or referenced by another entity.
-
C.
dataSupports
Indicates that one piece of data provides evidence, justification, or backing for the validity or reliability of another piece of data, claim, or conclusion.
-
D.
supportsDataRegion
Indicates that one entity is capable of operating with, storing, or otherwise handling data that resides in a specified geographic or logical data region.
-
E.
supportsDataExchange
Indicates that one entity enables or facilitates the transfer or sharing of data with 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.