Triple
T14087309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DRMAA API |
E339030
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | DRMAA |
E339030
|
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: DRMAA | Statement: [DRMAA API, abbreviation, DRMAA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DRMAA Context triple: [DRMAA API, abbreviation, DRMAA]
-
A.
DRMAA API
chosen
DRMAA API is a standardized programming interface that allows applications to submit and control jobs on distributed resource management and grid computing systems.
-
B.
Sun Grid Engine
Sun Grid Engine is an open-source batch-queuing and workload management system used to schedule and manage jobs on compute clusters and grids.
-
C.
YARN
YARN (Yet Another Resource Negotiator) is Hadoop’s cluster resource management and job scheduling framework that coordinates and allocates system resources for distributed data processing applications.
-
D.
SGE
SGE is a common abbreviation and nickname for Eintracht Frankfurt, a professional football club based in Frankfurt, Germany.
-
E.
ApplicationMaster
ApplicationMaster is the per-application coordinator in Hadoop YARN responsible for managing an application's lifecycle, resource requests, and task execution.
- 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.