Triple
T29012064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pascal API |
E736592
|
entity |
| Predicate | softwareDevelopmentParadigm |
P161698
|
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: [Pascal API, softwareDevelopmentParadigm, procedural programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareDevelopmentParadigm Context triple: [Pascal API, softwareDevelopmentParadigm, procedural programming]
-
A.
softwareParadigm
chosen
Indicates that a piece of software or a programming language follows or is based on a particular programming paradigm or style of development.
-
B.
programmingEvolution
Indicates how programming practices, languages, or paradigms change and develop over time.
-
C.
programmingParadigmWorkedOn
Indicates that an entity has worked on or been involved with a particular programming paradigm.
-
D.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
E.
softwareEngine
Indicates that an entity functions as a software engine, i.e., a core computational or processing component that drives or powers software operations for 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 9:43 a.m.