Triple
T28508455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nessus |
E721419
|
entity |
| Predicate | commercialEdition |
P31553
|
FINISHED |
| Object | Nessus Professional |
—
|
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: Nessus Professional | Statement: [Nessus, commercialEdition, Nessus Professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialEdition Context triple: [Nessus, commercialEdition, Nessus Professional]
-
A.
commercialProduct
chosen
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
-
B.
commercialAccess
Indicates that an entity is permitted to use or access something for commercial or profit-generating purposes.
-
C.
commercial
Indicates that one entity is engaged in a business-related or profit-oriented relationship, activity, or transaction with another entity.
-
D.
commercialSingle
Indicates that an entity is a commercially released single (a standalone commercial music or audio release).
-
E.
commercialService
Indicates a relationship where one entity provides a paid, profit-oriented service to another entity.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 3:10 a.m.