Triple
T7895046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Script Host |
E183323
|
entity |
| Predicate | cscript.exeRole |
P11936
|
FINISHED |
| Object | command-line script host |
—
|
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: command-line script host | Statement: [Windows Script Host, cscript.exeRole, command-line script host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cscript.exeRole Context triple: [Windows Script Host, cscript.exeRole, command-line script host]
-
A.
scriptContextRole
Indicates the role or function an entity plays within the context of a particular script or scripted interaction.
-
B.
scriptCodeRole
Indicates the role or function that a particular script code plays within a given context or system.
-
C.
scriptSystem
chosen
Indicates that one entity is the scripting or programming system used to control, configure, or automate the behavior of another entity.
-
D.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
-
E.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a174574819084270dbb6fcbb7fe |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92d94448190b4425bbfb64c658c |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:01 p.m.