Triple
T18221829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Ihaka |
E436324
|
entity |
| Predicate | RLanguageParadigm |
P49316
|
FINISHED |
| Object | functional 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: functional programming | Statement: [Ross Ihaka, RLanguageParadigm, functional programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RLanguageParadigm Context triple: [Ross Ihaka, RLanguageParadigm, functional programming]
-
A.
languageParadigm
chosen
Indicates a relationship where a programming language follows, supports, or is categorized under a particular programming paradigm.
-
B.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
C.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
D.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
-
E.
programmingLanguageFamily
Indicates that one programming language belongs to, or is categorized under, the family or lineage of another programming language.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e47c85108190bd9707b40bdfdb38 |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.