Triple
T33829228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capricornus |
E867050
|
entity |
| Predicate | zodiacSignModality |
P71952
|
FINISHED |
| Object | Cardinal |
—
|
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: Cardinal | Statement: [Capricornus, zodiacSignModality, Cardinal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zodiacSignModality Context triple: [Capricornus, zodiacSignModality, Cardinal]
-
A.
zodiacModality
chosen
Indicates the astrological modality (cardinal, fixed, or mutable) associated with a given zodiac sign.
-
B.
zodiacPolarity
Indicates the complementary energetic relationship (positive/negative or active/receptive) associated with a zodiac sign within an astrological system.
-
C.
zodiacRelation
Indicates a relationship between entities based on their positions or compatibility within the zodiac or astrological system.
-
D.
zodiacSystem
Indicates a relationship where an entity is associated with, defined by, or classified under a particular zodiac system or framework.
-
E.
zodiacElement
Indicates the elemental classification (such as fire, earth, air, or water) associated with a given zodiac sign.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:46 a.m.