Triple
T27799119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BackType |
E702191
|
entity |
| Predicate | usedProgrammingModel |
P21929
|
FINISHED |
| Object | stream processing |
—
|
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: stream processing | Statement: [BackType, usedProgrammingModel, stream processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProgrammingModel Context triple: [BackType, usedProgrammingModel, stream processing]
-
A.
hasProgrammingModel
Indicates that one entity defines, specifies, or is associated with the programming model used or supported by another entity.
-
B.
usedProgramModel
chosen
Indicates that an entity employed a specific program model as the basis or framework for its activities or operations.
-
C.
programmingParadigmWorkedOn
Indicates that an entity has worked on or been involved with a particular programming paradigm.
-
D.
softwareParadigm
Indicates that a piece of software or a programming language follows or is based on a particular programming paradigm or style of development.
-
E.
usedByProgrammingLanguages
Indicates that something (such as a tool, library, paradigm, or feature) is employed or utilized by one or more programming languages.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6380d35bc81908444d5038af3ffcb |
completed | May 2, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:33 p.m.