Triple
T3061172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows 32-bit |
E61998
|
entity |
| Predicate | hasRegistryView |
P44873
|
FINISHED |
| Object | single unified registry view for 32-bit apps |
—
|
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: single unified registry view for 32-bit apps | Statement: [Windows 32-bit, hasRegistryView, single unified registry view for 32-bit apps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegistryView Context triple: [Windows 32-bit, hasRegistryView, single unified registry view for 32-bit apps]
-
A.
hasView
Indicates that one entity provides a visual perspective or outlook onto another entity or scene.
-
B.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
C.
hasStandardRegister
Indicates that something is expressed or occurs in a standard, neutral, or non-marked linguistic register.
-
D.
definesRegistry
Indicates that one entity establishes or specifies a registry in which another entity is recorded or managed.
-
E.
maintainsRegistryOf
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e9e1e248190b5ed5ebcdad1321e |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.