Triple
T28296186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CBASIC |
E713577
|
entity |
| Predicate | programmingLanguageParadigm |
P49316
|
FINISHED |
| Object | procedural programming |
—
|
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: procedural programming | Statement: [CBASIC, programmingLanguageParadigm, procedural programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingLanguageParadigm Context triple: [CBASIC, programmingLanguageParadigm, procedural programming]
-
A.
languageParadigm
chosen
Indicates a relationship where a programming language follows, supports, or is categorized under a particular programming paradigm.
-
B.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
C.
programmingParadigmWorkedOn
Indicates that an entity has worked on or been involved with a particular programming paradigm.
-
D.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
E.
softwareParadigm
Indicates that a piece of software or a programming language follows or is based on a particular programming paradigm or style of development.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 11:32 p.m.