Triple
T15108390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10gen |
E360846
|
entity |
| Predicate | primaryProgrammingLanguageOfMainProduct |
P36279
|
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: [10gen, primaryProgrammingLanguageOfMainProduct, C++]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryProgrammingLanguageOfMainProduct Context triple: [10gen, primaryProgrammingLanguageOfMainProduct, C++]
-
A.
languageOfPrimaryProgramming
chosen
Indicates the programming language that is primarily used to implement or develop a given entity.
-
B.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
C.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
D.
developedPrimarilyIn
Indicates that something was mainly created, advanced, or brought into its primary form within a particular context, place, or domain, even if contributions occurred elsewhere.
-
E.
projectLanguageCode
Indicates the programming or markup language used in a project, represented by its standardized language code.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0058af8988190977d998f85893836 |
completed | April 15, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69deb96c1d9c81909351558ed97bc5b7 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:05 a.m.