Triple
T26853160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Aurora |
E676111
|
entity |
| Predicate | awakeningCondition |
P29885
|
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: [Princess Aurora, awakeningCondition, true love's kiss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awakeningCondition Context triple: [Princess Aurora, awakeningCondition, 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.
conveningCondition
Indicates the circumstances or requirements under which a meeting, gathering, or formal session is initiated or brought together.
-
C.
releaseCondition
Indicates the circumstances or requirements under which something is allowed to be released or made available.
-
D.
triggerCondition
chosen
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
E.
captureCondition
Indicates the specific circumstances or criteria under which a capture event or action is triggered or considered valid.
- 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61b93f6d88190beffbcd2e9374a61 |
completed | May 2, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:18 a.m.