Triple
T27102326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dial of Destiny |
E686473
|
entity |
| Predicate | isDesiredFor |
P161851
|
FINISHED |
| Object | altering historical events |
—
|
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: altering historical events | Statement: [Dial of Destiny, isDesiredFor, altering historical events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDesiredFor Context triple: [Dial of Destiny, isDesiredFor, altering historical events]
-
A.
isDesiredFor
chosen
Indicates that one entity is wanted, preferred, or sought after for use, benefit, or association with another entity.
-
B.
describesDesireFor
Indicates that one entity expresses or conveys a wish, longing, or aspiration directed toward another entity or outcome.
-
C.
wantedBy
Indicates that one entity is desired, sought, or wished for by another entity.
-
D.
indicatedFor
Indicates...that one entity (typically a treatment, procedure, or product) is recommended or appropriate for use in relation to another entity (such as a condition, symptom, or patient group).
-
E.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f623b76bec8190ad8f66180c8ecbd4 |
completed | May 2, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:48 a.m.