Triple
T34507336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSKY interface |
E885922
|
entity |
| Predicate | interactionParadigm |
P195947
|
FINISHED |
| Object | VERB-NOUN command structure |
—
|
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: VERB-NOUN command structure | Statement: [DSKY interface, interactionParadigm, VERB-NOUN command structure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionParadigm Context triple: [DSKY interface, interactionParadigm, VERB-NOUN command structure]
-
A.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
B.
controlInteraction
Indicates an interaction in which one entity directs, regulates, or constrains the behavior or state of another.
-
C.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
-
D.
interactiveElement
Indicates that one entity functions as an interface component designed to receive and respond to user actions initiated by another entity.
-
E.
interactive
Indicates that one entity engages in reciprocal or two-way communication or action with another entity.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: May 1, 2026, 2:01 a.m.