Triple
T28390643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flip 3D |
E719147
|
entity |
| Predicate | notAvailableInVersion |
P81687
|
FINISHED |
| Object | Windows 8 |
—
|
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 8 | Statement: [Flip 3D, notAvailableInVersion, Windows 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAvailableInVersion Context triple: [Flip 3D, notAvailableInVersion, Windows 8]
-
A.
notAvailableOnEdition
chosen
Indicates that something is excluded from or cannot be used in a particular edition or version.
-
B.
notAvailableFor
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
C.
alsoAvailableInVersion
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
D.
notSupportedBy
Indicates that an entity does not receive assistance, endorsement, or backing from another entity.
-
E.
notDirectlyAvailableFor
Indicates that an entity cannot be accessed, used, or obtained immediately or without intermediaries, but may be reachable through indirect means or additional steps.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64cec950881909d89fd56511514a2 |
completed | May 2, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:13 a.m.