Triple
T16853055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | webOS |
E409720
|
entity |
| Predicate | supportsScreenMirroring |
P31547
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [webOS, supportsScreenMirroring, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsScreenMirroring Context triple: [webOS, supportsScreenMirroring, true]
-
A.
supportsDisplayTechnology
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
-
B.
supportsExternalDisplay
chosen
Indicates that an entity is capable of connecting to and functioning with an external display device.
-
C.
supportsSplitScreen
Indicates that one entity enables or is compatible with displaying multiple views or applications simultaneously in a split-screen layout.
-
D.
supportsRemotePlay
Indicates that one entity enables or is compatible with remote play functionality for another entity.
-
E.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37abadc81909d02d329403497d6 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.