Triple
T9576090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Innoventions |
E231048
|
entity |
| Predicate | featuredTheme |
P25955
|
FINISHED |
| Object | home technology |
—
|
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: home technology | Statement: [Innoventions, featuredTheme, home technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredTheme Context triple: [Innoventions, featuredTheme, home technology]
-
A.
featuresThemeType
Indicates that something (such as a work, event, or item) has or is characterized by a particular type of theme.
-
B.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
C.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
D.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in another entity.
-
E.
themeHighlights
Indicates that certain elements are emphasized or visually distinguished as key features within a particular theme.
- 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_69ca848091c48190bc313d6620d09555 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99ac17a48190bb8448394f22b1e9 |
completed | April 1, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69ccd59b960c8190966a8870a2426bd5 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:05 p.m.