Triple
T23439918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palms and Runes, Tarot and Tea |
E565365
|
entity |
| Predicate | hasDivinationSystem |
P23889
|
FINISHED |
| Object | palmistry |
—
|
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: palmistry | Statement: [Palms and Runes, Tarot and Tea, hasDivinationSystem, palmistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDivinationSystem Context triple: [Palms and Runes, Tarot and Tea, hasDivinationSystem, palmistry]
-
A.
hasRitualSystem
Indicates that an entity possesses or is associated with a structured set of rituals or ceremonial practices.
-
B.
divinationMethod
chosen
Indicates the method or technique used to perform a divinatory act or practice.
-
C.
hasMagicSystemElement
Indicates that an entity’s magic system includes or is characterized by a specific elemental component or aspect.
-
D.
hasRitualElements
Indicates that one entity incorporates, contains, or is characterized by ritualistic components, practices, or features associated with formalized ceremonies or rites.
-
E.
hasRitualSpace
Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5df28288190936f16b017a20bc0 |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.