Triple
T21077736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mackenzie Poltergeist legend |
E519281
|
entity |
| Predicate | hasBeliefStatus |
P142749
|
FINISHED |
| Object | contested |
—
|
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: contested | Statement: [Mackenzie Poltergeist legend, hasBeliefStatus, contested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeliefStatus Context triple: [Mackenzie Poltergeist legend, hasBeliefStatus, contested]
-
A.
hasVariantBelief
Indicates that one entity holds a belief that is an alternative or differing version of another entity’s belief.
-
B.
requiresBeliefIn
Indicates that one entity can only be valid, accessible, or fulfilled if belief in another specified entity or proposition is held.
-
C.
invokesBeliefIn
Indicates that one entity causes, triggers, or calls upon a belief or mental acceptance of something in another entity.
-
D.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
E.
hasCentralBelief
Indicates that a particular belief is a core or foundational belief within an entity’s overall belief system.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d857388190bdc17dcda6c7bc9d |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:49 p.m.