Triple
T19356323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endymion |
E484155
|
entity |
| Predicate | causeOfSleep |
P122823
|
FINISHED |
| Object | request for eternal youth (in some versions) |
—
|
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: request for eternal youth (in some versions) | Statement: [Endymion, causeOfSleep, request for eternal youth (in some versions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfSleep Context triple: [Endymion, causeOfSleep, request for eternal youth (in some versions)]
-
A.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeOfIllness
Indicates that one entity is the reason or source responsible for another entity’s illness or disease.
-
C.
causeOfWeakness
Indicates that one entity is the reason or source that brings about the weakness of another entity.
-
D.
causeInStory
chosen
Indicates that one event, action, or state functions as the cause of another within the narrative structure of a story.
-
E.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e61908920c8190833051e30ad2420c |
completed | April 20, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e4dd13a8cc81909cd02668564c9f29 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.