Triple
T38637635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Sanderson |
E937604
|
entity |
| Predicate | usesDesignPattern |
P191760
|
FINISHED |
| Object | Model–View–ViewModel (MVVM) |
—
|
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: Model–View–ViewModel (MVVM) | Statement: [Steve Sanderson, usesDesignPattern, Model–View–ViewModel (MVVM)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDesignPattern Context triple: [Steve Sanderson, usesDesignPattern, Model–View–ViewModel (MVVM)]
-
A.
usesDesignModel
Indicates that one entity applies or relies on a particular design model in performing its function or defining its structure.
-
B.
usedDesignFeature
Indicates that one entity employed or incorporated a particular design feature in its creation, implementation, or functionality.
-
C.
usesDesignationPattern
Indicates that one entity applies or follows a specific designation pattern in how it names or labels something.
-
D.
hasUsePattern
Indicates a characteristic or recurring way in which something is typically used or applied.
-
E.
designedForServicePattern
Indicates that something has been created or configured specifically to support, implement, or conform to a particular service pattern.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69fce76669408190b1beef8899a8a5e2 |
completed | May 7, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:32 p.m.