Triple
T33083850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demetri Noh |
E846578
|
entity |
| Predicate | hasFutureVision |
P26266
|
FINISHED |
| Object | premonition of his own death |
—
|
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: premonition of his own death | Statement: [Demetri Noh, hasFutureVision, premonition of his own death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFutureVision Context triple: [Demetri Noh, hasFutureVision, premonition of his own death]
-
A.
hasVisionOf
chosen
Indicates that one entity perceives, imagines, or foresees another entity or scenario, typically in a mental, prophetic, or visualized form.
-
B.
containsVisionOf
Indicates that one entity includes, depicts, or embodies a visual representation or image of another entity.
-
C.
hasFutureTimeline
Indicates that an entity is associated with a projected or planned sequence of events extending into the future.
-
D.
envisionedTechnology
Indicates that an entity has imagined, conceptualized, or planned a particular technology, typically before it exists or is realized.
-
E.
visionOf
Indicates that one entity is a visual representation, image, or depiction of 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:26 a.m.