Triple
T33671818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE-225 |
E862636
|
entity |
| Predicate | associatedProgrammingLanguage |
P36279
|
FINISHED |
| Object | Dartmouth BASIC |
E245826
|
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: Dartmouth BASIC | Statement: [GE-225, associatedProgrammingLanguage, Dartmouth BASIC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedProgrammingLanguage Context triple: [GE-225, associatedProgrammingLanguage, Dartmouth BASIC]
-
A.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
B.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
C.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
D.
languageOfPrimaryProgramming
chosen
Indicates the programming language that is primarily used to implement or develop a given entity.
-
E.
alsoUsedLanguageInProgramming
Indicates that an entity used an additional programming language, beyond a primary one, in the context of programming.
- F. None of above.
Provenance (4 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c6c38fc8190b840d5e3b1bfbb6f |
completed | June 20, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:43 a.m.