Triple
T32541810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night light |
E831731
|
entity |
| Predicate | activationCanBe |
P58199
|
FINISHED |
| Object | time-based |
—
|
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: time-based | Statement: [Night light, activationCanBe, time-based]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationCanBe Context triple: [Night light, activationCanBe, time-based]
-
A.
activationBy
Indicates that one entity initiates, triggers, or enhances the activity, function, or state of another entity.
-
B.
activationType
chosen
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
-
C.
activationProperty
Indicates a relationship where one entity specifies the conditions, parameters, or characteristics that determine how another entity becomes active or is triggered.
-
D.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
E.
enabledAction
Indicates that a particular action is permitted, activated, or available to be performed in the given 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:02 a.m.