Triple
T3286073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Santi |
E68984
|
entity |
| Predicate | supernaturalStatus |
P45145
|
FINISHED |
| Object | restless spirit |
—
|
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: restless spirit | Statement: [Santi, supernaturalStatus, restless spirit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supernaturalStatus Context triple: [Santi, supernaturalStatus, restless spirit]
-
A.
containsSupernaturalElement
Indicates that the subject involves or features a supernatural, magical, or otherworldly element beyond normal natural laws.
-
B.
sacredStatus
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
C.
associatedSpirit
chosen
Indicates a relationship where one entity is linked to or accompanied by a particular spirit, often as a guide, protector, or defining supernatural presence.
-
D.
hasSuperstition
Indicates that one entity holds or practices a particular superstition related to another entity or concept.
-
E.
primarySpirit
Indicates that one entity is the main or most fundamental spiritual essence 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03918c48190987d7cfd3bda9716 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.