Triple
T6525073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LabVIEW |
E151280
|
entity |
| Predicate | hasUIElement |
P54128
|
FINISHED |
| Object | controls |
—
|
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: controls | Statement: [LabVIEW, hasUIElement, controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUIElement Context triple: [LabVIEW, hasUIElement, controls]
-
A.
hasControlElement
chosen
Indicates that one entity includes or is associated with a component specifically intended to control, regulate, or influence its behavior or operation.
-
B.
usesElement
Indicates that one entity makes use of, incorporates, or depends on a specified element in its structure, function, or behavior.
-
C.
hasTextElement
Indicates that an entity contains or is associated with a specific text-based component or segment.
-
D.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
E.
hasProgramElement
Indicates that one entity contains, includes, or is associated with a specific program element (such as a function, class, module, or code component).
- 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.