Triple
T21726718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hermit |
E536291
|
entity |
| Predicate | positionInMajorArcana |
P145111
|
FINISHED |
| Object | 9th card |
—
|
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: 9th card | Statement: [The Hermit, positionInMajorArcana, 9th card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMajorArcana Context triple: [The Hermit, positionInMajorArcana, 9th card]
-
A.
hasNumberOfCardsInMajorArcana
Indicates the specific count of cards that an entity has within the Major Arcana subset of a tarot deck.
-
B.
hasNumberOfCardsInMinorArcana
Indicates the specific count of cards that an entity possesses within the Minor Arcana subset of a tarot deck.
-
C.
associatedTarotPathInSomeSystems
Indicates that, in certain interpretive or esoteric systems, one entity is linked or mapped to a particular path within the Tarot framework.
-
D.
positionInSriYantra
Indicates the specific spatial location or role that an element occupies within the geometric structure of the Sri Yantra.
-
E.
positionInAsterism
Indicates the specific location or role that an object occupies within a defined asterism pattern.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd973ac648190bb09e20ac1be2d9b |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:48 p.m.