Triple
T11983120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurora |
E285207
|
entity |
| Predicate | awakeningCause |
P694
|
FINISHED |
| Object | true love's kiss |
—
|
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: true love's kiss | Statement: [Aurora, awakeningCause, true love's kiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awakeningCause Context triple: [Aurora, awakeningCause, true love's kiss]
-
A.
awakensIn
Indicates that one entity comes out of sleep or becomes conscious while located within or inside another entity.
-
B.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
typicalActivationReason
Indicates the usual or most common reason why an entity, process, or condition becomes activated or triggered.
-
D.
wakeWord
Indicates that one entity serves as the activation phrase or trigger word used to wake up or activate another entity (such as a device or system).
-
E.
ageOfAwakening
Indicates the specific age at which an entity becomes aware, conscious, or begins its significant period of activity or development.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.