Triple
T19401893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microsoft Office 97 |
E485343
|
entity |
| Predicate | availableEdition |
P44721
|
FINISHED |
| Object | Standard Edition |
—
|
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: Standard Edition | Statement: [Microsoft Office 97, availableEdition, Standard Edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableEdition Context triple: [Microsoft Office 97, availableEdition, Standard Edition]
-
A.
hasEditionIn
chosen
Indicates that one entity has a specific edition or version that exists or is available in another entity (such as a particular format, language, or location).
-
B.
numberOfEditions
Indicates the total count of distinct editions associated with a given entity.
-
C.
hasDifferentEditions
Indicates that an entity exists in multiple distinct versions or editions that differ in some characteristics.
-
D.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
-
E.
languageOfAvailableEditions
Indicates the language in which the available editions of a work or resource are published.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62577454c81909d5bcd07e99b27e4 |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.