Triple
T33405587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarah (mother) |
E855428
|
entity |
| Predicate | interactsWithTechnology |
P81781
|
FINISHED |
| Object | kitchen appliances |
—
|
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: kitchen appliances | Statement: [Sarah (mother), interactsWithTechnology, kitchen appliances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactsWithTechnology Context triple: [Sarah (mother), interactsWithTechnology, kitchen appliances]
-
A.
associatedWithTechnology
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
B.
technologyInteractedWith
chosen
Indicates that an entity has used, engaged with, or otherwise interacted with a particular technology.
-
C.
usesTechnologyInStory
Indicates that an entity incorporates or employs a particular technology within the context of a narrative or story.
-
D.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
E.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 1, 2026, 1:36 a.m.