Triple
T14086611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RISC II |
E339012
|
entity |
| Predicate | supportsRegisterWindows |
P112757
|
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: [RISC II, supportsRegisterWindows, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRegisterWindows Context triple: [RISC II, supportsRegisterWindows, true]
-
A.
supportsMultipleWindows
Indicates that the subject can handle or display more than one window or view simultaneously.
-
B.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
-
C.
supportsWindowSystem
Indicates that one entity provides compatibility with, or operational support for, a particular windowing system used to manage graphical user interfaces.
-
D.
usesWindowsAPI
Indicates that one entity makes use of the Windows operating system’s application programming interfaces (APIs) to perform its functions or interactions.
-
E.
hasWindowsShape
Indicates that an object possesses a particular geometric or stylistic form characteristic of windows.
- F. None of above. chosen
Provenance (4 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5edff1b881909ea56dc2429ef2dd |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de2398856c81908bed6070e4ca6ab1 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:21 p.m.