Triple
T15063829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pet Sematary II |
E379703
|
entity |
| Predicate | hasCursedLocation |
P117176
|
FINISHED |
| Object | Micmac burial ground |
—
|
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: Micmac burial ground | Statement: [Pet Sematary II, hasCursedLocation, Micmac burial ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCursedLocation Context triple: [Pet Sematary II, hasCursedLocation, Micmac burial ground]
-
A.
hasAltarLocation
Indicates that an altar is situated at or associated with a specific location.
-
B.
hasVillainBaseLocation
Indicates that a villain’s primary base or headquarters is located at a specified place.
-
C.
exileLocation
Indicates the place or destination to which an entity is sent or kept in exile.
-
D.
hasNumberOfFalseDoors
Indicates that an entity is associated with a specific count of false doors (door-like architectural features that do not function as actual entrances or exits).
-
E.
hasDungeon
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dedee803ac81908bb7d66e49c2eb72 |
completed | April 15, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:02 a.m.