Triple
T24006843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Snake |
E594411
|
entity |
| Predicate | yinYangType |
P71953
|
FINISHED |
| Object | Yin |
—
|
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: Yin | Statement: [Year of the Snake, yinYangType, Yin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yinYangType Context triple: [Year of the Snake, yinYangType, Yin]
-
A.
associatedWithYinYang
Indicates a relationship in which something is conceptually, symbolically, or functionally linked to the dualistic principles of Yin and Yang.
-
B.
zodiacModality
Indicates the astrological modality (cardinal, fixed, or mutable) associated with a given zodiac sign.
-
C.
zodiacElement
Indicates the elemental classification (such as fire, earth, air, or water) associated with a given zodiac sign.
-
D.
zodiacPolarity
chosen
Indicates the complementary energetic relationship (positive/negative or active/receptive) associated with a zodiac sign within an astrological system.
-
E.
yakshini
Indicates a mythological or spiritual association involving a yakshini, such as being protected by, devoted to, influenced by, or otherwise connected to this female nature spirit.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46a6ba48190b0cce0b134dfb35f |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.