Triple
T14341334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DLS |
E355610
|
entity |
| Predicate | languageCategory |
P113876
|
FINISHED |
| Object | dynamic programming languages |
—
|
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: dynamic programming languages | Statement: [DLS, languageCategory, dynamic programming languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCategory Context triple: [DLS, languageCategory, dynamic programming languages]
-
A.
languageLabel
Indicates the human-readable name or label of a language associated with an entity or resource.
-
B.
languageSpecifies
Indicates that one entity defines or constrains the syntax, semantics, or usage rules that govern how another language or linguistic system is expressed or interpreted.
-
C.
languageArea
Indicates the geographic or cultural region in which a particular language is used or predominantly spoken.
-
D.
languageUse
Indicates the language or languages an entity uses for communication, expression, or interaction.
-
E.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e87febc8190a63c668cbd0fd713 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:14 a.m.