Triple
T20191792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alear |
E492993
|
entity |
| Predicate | awakensFrom |
P115338
|
FINISHED |
| Object | a thousand-year slumber |
—
|
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: a thousand-year slumber | Statement: [Alear, awakensFrom, a thousand-year slumber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awakensFrom Context triple: [Alear, awakensFrom, a thousand-year slumber]
-
A.
awakensIn
Indicates that one entity comes out of sleep or becomes conscious while located within or inside another entity.
-
B.
ageOfAwakening
Indicates the specific age at which an entity becomes aware, conscious, or begins its significant period of activity or development.
-
C.
raisedFrom
Indicates that one entity has been elevated, derived, or brought up from another prior state, source, or condition.
-
D.
reemergesAs
Indicates that an entity that previously disappeared, transformed, or became inactive later appears again in a new or altered form.
-
E.
revivedAfter
chosen
Indicates that one entity comes back to life or is restored to a living or active state after a period of being dead, inactive, or nonfunctional, following another event or time point.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad593f88190a1e534fed38b3cd7 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.