Triple
T3414037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PADL |
E71964
|
entity |
| Predicate | languageParadigm |
P49316
|
FINISHED |
| Object | declarative programming paradigm |
—
|
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: declarative programming paradigm | Statement: [PADL, languageParadigm, declarative programming paradigm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageParadigm Context triple: [PADL, languageParadigm, declarative programming paradigm]
-
A.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
B.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
C.
languageOfCode
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
D.
programmingLanguageFamily
Indicates that one programming language belongs to, or is categorized under, the family or lineage of another programming language.
-
E.
languageNeutral
Indicates that the relationship or action is independent of any specific natural language, applying uniformly across different linguistic contexts.
- F. None of above. chosen
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_69ad85ac312481909e7027ced1456a9f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb927e8d081908a5ab283da93beb2 |
completed | March 8, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69adadfcbc38819080852c18240451c5 |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb23d23088190aeafe1379eae2eaa |
completed | March 8, 2026, 5:30 p.m. |
Created at: March 8, 2026, 3:15 p.m.