Triple
T28509236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Sullo |
E721437
|
entity |
| Predicate | toolCreatedCategory |
P37347
|
FINISHED |
| Object | web server security scanner |
—
|
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: web server security scanner | Statement: [Chris Sullo, toolCreatedCategory, web server security scanner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolCreatedCategory Context triple: [Chris Sullo, toolCreatedCategory, web server security scanner]
-
A.
createsCategory
Indicates that one entity establishes or brings into existence a new category for organizing or classifying other entities.
-
B.
sampleCategory
Indicates that an item or instance belongs to, or is classified under, a particular sample category.
-
C.
creationType
Indicates the manner or process by which something was brought into existence or produced.
-
D.
toolType
Indicates the specific kind or category of tool associated with an entity.
-
E.
toolDeveloperFor
chosen
Indicates that one entity is the creator or developer of a tool that is used by or associated with 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_69f64f7388a88190a80dc4730f92eded |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:11 a.m.