Triple
T4769432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarot |
E105888
|
entity |
| Predicate | hasNumberOfCardsInMinorArcana |
P58673
|
FINISHED |
| Object | 56 |
—
|
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: 56 | Statement: [Tarot, hasNumberOfCardsInMinorArcana, 56]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfCardsInMinorArcana Context triple: [Tarot, hasNumberOfCardsInMinorArcana, 56]
-
A.
associatedTarotPathInSomeSystems
Indicates that, in certain interpretive or esoteric systems, one entity is linked or mapped to a particular path within the Tarot framework.
-
B.
hasNotableCardFamily
Indicates that an entity is associated with a specific, distinguished group or family of related cards.
-
C.
numberOfDecks
Indicates the quantity of decks associated with or contained in an entity.
-
D.
hasNumberOfArches
Indicates the relationship specifying how many arches are present in or associated with a given entity.
-
E.
cardGameAssociatedWith
Indicates that there is a relationship of association between a card game and another entity, such as a person, place, event, or concept.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd6508e218819086a36236cfa4a249 |
completed | March 20, 2026, 3:17 p.m. |
Created at: March 20, 2026, 1:21 p.m.