Triple
T15625399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Child's Play (2019 film) |
E375663
|
entity |
| Predicate | technologyElement |
P1482
|
FINISHED |
| Object | smart home integration |
—
|
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: smart home integration | Statement: [Child's Play (2019 film), technologyElement, smart home integration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyElement Context triple: [Child's Play (2019 film), technologyElement, smart home integration]
-
A.
technologyPresent
Indicates that a particular technology exists, is available, or is currently in use in the given context or situation.
-
B.
technologyType
chosen
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologyIncludes
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
-
D.
technologyDiscussed
Indicates that a conversation, text, or interaction includes discussion or mention of a particular technology.
-
E.
technologyClass
Indicates the classification or category of technology to which an entity belongs.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9e5e248190ae54cda1fde51efb |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.