Triple
T22650213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solid Start |
E559070
|
entity |
| Predicate | officialFrameworkFor |
P9140
|
FINISHED |
| Object | SolidJS full-stack development |
—
|
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: SolidJS full-stack development | Statement: [Solid Start, officialFrameworkFor, SolidJS full-stack development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialFrameworkFor Context triple: [Solid Start, officialFrameworkFor, SolidJS full-stack development]
-
A.
frameworkFor
chosen
Indicates that one entity serves as a supporting structure, system, or basis that organizes, guides, or enables the development or functioning of another entity.
-
B.
parentFramework
Indicates that one framework serves as the higher-level or containing framework from which another framework is derived, organized, or structured.
-
C.
frameworkPresented
Indicates that a particular framework has been formally introduced or shown to an audience or recipient.
-
D.
adoptedFrameworkType
Indicates that one entity has chosen and is using a particular framework type as its adopted standard or approach.
-
E.
appliesFramework
Indicates that one entity uses or implements a particular framework in relation to another entity or context.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703b40b88190aec5cf2fa28bfcbf |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.