Triple
T14087331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DRMAA API |
E339030
|
entity |
| Predicate | hasLanguageBinding |
P83858
|
FINISHED |
| Object | C |
—
|
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: C | Statement: [DRMAA API, hasLanguageBinding, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageBinding Context triple: [DRMAA API, hasLanguageBinding, C]
-
A.
supportsLanguageBindingSystem
chosen
Indicates that one entity provides mechanisms or infrastructure that enable another entity to create, use, or integrate language bindings for a system or platform.
-
B.
hasLanguageType
Indicates that an entity is associated with a particular type or category of language (e.g., spoken, written, programming, sign).
-
C.
hasLanguageOn
Indicates that an entity uses or is associated with a particular language in a specific context, medium, or location.
-
D.
hasLanguageContext
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
-
E.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee1ce88819091c983286289337e |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.