Triple
T35081625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamia (Drag Me to Hell) |
E1012451
|
entity |
| Predicate | realmOfDestination |
P21947
|
FINISHED |
| Object | hell |
—
|
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: hell | Statement: [Lamia (Drag Me to Hell), realmOfDestination, hell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmOfDestination Context triple: [Lamia (Drag Me to Hell), realmOfDestination, hell]
-
A.
journeyDestination
chosen
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
B.
regionOfTour
Indicates that a specified geographic or administrative region is the location or scope within which a particular tour takes place.
-
C.
territoryOfDestination
Indicates that a specified territory is the destination or endpoint location associated with an action, movement, or relation.
-
D.
travelScope
Indicates the extent or range within which travel is allowed, intended, or applicable for an entity or activity.
-
E.
realm
Indicates that one entity is a domain, sphere of influence, or area of control associated 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.