Triple
T27583565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDS |
E699637
|
entity |
| Predicate | hasProgrammingLanguageBindings |
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: [DDS, hasProgrammingLanguageBindings, C++]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProgrammingLanguageBindings Context triple: [DDS, hasProgrammingLanguageBindings, C++]
-
A.
hasLanguageOfProgramming
Indicates that an entity uses, is implemented in, or is otherwise associated with a particular programming language.
-
B.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
-
C.
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.
-
D.
languageOfImplementation
Indicates the programming language in which a given software system, component, or algorithm is implemented.
-
E.
languageTypeCovered
Indicates that one entity provides coverage, support, or applicability for a particular type or category of language associated with another entity.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 27, 2026, 2:03 p.m.