Triple
T12913643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prismo |
E308921
|
entity |
| Predicate | ruleOfWishes |
P106980
|
FINISHED |
| Object | wishes must be specific |
—
|
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: wishes must be specific | Statement: [Prismo, ruleOfWishes, wishes must be specific]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleOfWishes Context triple: [Prismo, ruleOfWishes, wishes must be specific]
-
A.
makesWish
Indicates that an entity expresses a desire or hope for something to happen or become true.
-
B.
lastWish
Indicates that one entity is the final desire, request, or intention expressed by another entity, typically before death or the end of a significant event.
-
C.
fulfilledWish
Indicates that a previously expressed wish or desire has been successfully realized or brought about.
-
D.
promiseOfBlessingTo
Indicates that one entity has declared or assured a future blessing or favorable outcome to another entity.
-
E.
enchantedBy
Indicates that one entity has cast or holds a magical enchantment over another entity.
- F. None of above. chosen
Provenance (4 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971a0d6508190bca9668e9e06abfe |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9708a86bc8190bcdcf97e845bb413 |
completed | April 10, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:41 p.m.