Triple
T28583912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aero Glass |
E723441
|
entity |
| Predicate | disabledInEdition |
P81687
|
FINISHED |
| Object | Windows Vista Starter |
—
|
NE NERFINISHED |
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: Windows Vista Starter | Statement: [Aero Glass, disabledInEdition, Windows Vista Starter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disabledInEdition Context triple: [Aero Glass, disabledInEdition, Windows Vista Starter]
-
A.
notAvailableOnEdition
chosen
Indicates that something is excluded from or cannot be used in a particular edition or version.
-
B.
hasEditionFeature
Indicates that one edition of a work includes a specific feature, characteristic, or component that distinguishes it from other editions.
-
C.
disabledByDefaultIn
Indicates that a feature, capability, or setting is turned off by default within the specified context or environment.
-
D.
hasEditionIn
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).
-
E.
includedInEdition
Indicates that one item (such as a work, text, or component) is contained within or forms part of a particular edition.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:16 a.m.