Triple
T31770842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OS/8 |
E810933
|
entity |
| Predicate | supportsOverlayMechanism |
P203
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [OS/8, supportsOverlayMechanism, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsOverlayMechanism Context triple: [OS/8, supportsOverlayMechanism, yes]
-
A.
supportsSlideOver
Indicates that one entity enables or is compatible with displaying another entity in a slide-over (partially overlaid) interface or view.
-
B.
backedByMechanism
Indicates that something is supported, enabled, or made possible by an underlying mechanism or system.
-
C.
supportsOverscan
Indicates that a display device or system is capable of handling overscan, meaning it can properly show content that extends beyond the nominal visible screen area.
-
D.
overlays
Indicates that one entity is placed on top of or superimposed over another, partially or completely covering it in the same spatial area.
-
E.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:33 p.m.