Triple
T23423997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norton Utilities for the IBM PC |
E560740
|
entity |
| Predicate | softwareVersionOf |
P31922
|
FINISHED |
| Object | Norton Utilities |
—
|
NE NERFINISHED |
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: Norton Utilities | Statement: [Norton Utilities for the IBM PC, softwareVersionOf, Norton Utilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareVersionOf Context triple: [Norton Utilities for the IBM PC, softwareVersionOf, Norton Utilities]
-
A.
versionOf
chosen
Indicates that one entity is a specific form, edition, or variant derived from or corresponding to another entity.
-
B.
exportVersionOf
Indicates that one entity is a version of another specifically created or designated for export (e.g., for external distribution or use).
-
C.
softwareFormat
Indicates that one entity specifies or uses the file or data format in which a software-related item is encoded, stored, or delivered.
-
D.
softwareName
Indicates that one entity is the name or title of a software application associated with another entity.
-
E.
exportVersion
Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54838fc8190a3205ca72daaf107 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.