Triple
T14086610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RISC II |
E339012
|
entity |
| Predicate | registerWindowing |
P31211
|
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: [RISC II, registerWindowing, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registerWindowing Context triple: [RISC II, registerWindowing, yes]
-
A.
windowManagement
chosen
Indicates the relationship or action of controlling, arranging, or interacting with on-screen windows within a graphical user interface.
-
B.
registrationContext
Indicates the situational or environmental context under which a registration event occurs, such as conditions, purpose, or setting.
-
C.
windowType
Indicates the specific kind or category of window associated with an entity.
-
D.
registrationEffect
Indicates the outcome or consequence that results from an entity being registered or from the act of registration taking place.
-
E.
registrationPort
Indicates the port number on which a service or component is registered to receive connections or requests.
- 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_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. |
Created at: April 9, 2026, 10:21 p.m.