Triple
T14087327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DRMAA API |
E339030
|
entity |
| Predicate | usedWith |
P4791
|
FINISHED |
| Object | Univa Grid Engine |
E68045
|
NE 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: Univa Grid Engine | Statement: [DRMAA API, usedWith, Univa Grid Engine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Univa Grid Engine Context triple: [DRMAA API, usedWith, Univa Grid Engine]
-
A.
Sun Grid Engine
chosen
Sun Grid Engine is an open-source batch-queuing and workload management system used to schedule and manage jobs on compute clusters and grids.
-
B.
SGE
SGE is a common abbreviation and nickname for Eintracht Frankfurt, a professional football club based in Frankfurt, Germany.
-
C.
Compuware Arena
Compuware Arena is a multi-purpose ice hockey venue in Plymouth Township, Michigan, best known as the longtime home of the OHL’s Plymouth Whalers.
-
D.
Workload Manager
Workload Manager is a system or software component that monitors, prioritizes, and allocates computing resources to different tasks or applications to optimize overall performance and efficiency.
-
E.
z/OS Workload Manager
z/OS Workload Manager is an IBM mainframe component that dynamically manages system resources to meet performance goals and service levels for workloads running on the z/OS operating system.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0a3e55c81909b52f618e9076dd2 |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:21 p.m.