Triple
T6525066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LabVIEW |
E151280
|
entity |
| Predicate | supportsProgrammingConcept |
P51750
|
FINISHED |
| Object | parallel execution |
—
|
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: parallel execution | Statement: [LabVIEW, supportsProgrammingConcept, parallel execution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProgrammingConcept Context triple: [LabVIEW, supportsProgrammingConcept, parallel execution]
-
A.
programmingIncludes
Indicates that one programming-related entity contains, incorporates, or makes use of another as a part, feature, or component.
-
B.
supportedParadigm
Indicates that one entity (such as a tool, language, or system) provides functionality or features that enable or are compatible with a particular paradigm or methodological approach.
-
C.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
D.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
E.
programmingFeature
chosen
Indicates a relationship where one entity is a specific programming-related capability, construct, or functionality provided or supported by another entity (such as a language, tool, or system).
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad9831f88190a2b64cf6bc8c9a11 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.