Triple
T26376233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exceptional C++ |
E660908
|
entity |
| Predicate | programmingLanguageCovered |
P129871
|
FINISHED |
| Object | C++ |
—
|
NE NERFINISHED |
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: [Exceptional C++, programmingLanguageCovered, C++]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingLanguageCovered Context triple: [Exceptional C++, programmingLanguageCovered, C++]
-
A.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
B.
languageTypeCovered
chosen
Indicates that one entity provides coverage, support, or applicability for a particular type or category of language associated with another entity.
-
C.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
D.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
E.
programmingLanguageDescribed
Indicates that one entity provides a description or documentation of a particular programming 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 26, 2026, 11:01 p.m.