Triple
T30316081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaScript for Automation |
E771057
|
entity |
| Predicate | scriptingInterface |
P11936
|
FINISHED |
| Object | osascript command-line tool |
—
|
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: osascript command-line tool | Statement: [JavaScript for Automation, scriptingInterface, osascript command-line tool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptingInterface Context triple: [JavaScript for Automation, scriptingInterface, osascript command-line tool]
-
A.
appliesToScript
Indicates that something (such as a rule, configuration, or operation) is specifically relevant or applicable to a given script.
-
B.
scriptEditor
Indicates that an entity serves as the editor or editing environment used to create or modify a script.
-
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.
canBeScripted
Indicates that the action or behavior can be defined, controlled, or automated through a script or scripting mechanism.
-
E.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 7:51 p.m.