Triple
T34085599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shravana Nakshatra |
E874167
|
entity |
| Predicate | secondPadaRashiNavamsa |
P62306
|
FINISHED |
| Object | Taurus |
—
|
NE NERFINISHED |
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: Taurus | Statement: [Shravana Nakshatra, secondPadaRashiNavamsa, Taurus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondPadaRashiNavamsa Context triple: [Shravana Nakshatra, secondPadaRashiNavamsa, Taurus]
-
A.
hasSecondSunName
Indicates that an entity has a secondary or alternative name specifically associated with a sun or solar object.
-
B.
secondElement
chosen
Indicates that one entity is the second element in an ordered pair, sequence, or collection relative to another entity.
-
C.
secondaryPosition
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
D.
secondSyllable
Indicates that the second syllable of one linguistic unit corresponds to, matches, or is identified as a particular syllable or sound in relation to another entity.
-
E.
secondPhase
Indicates that an entity is in, or has progressed to, the second phase or stage of a multi-phase process or sequence.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:52 a.m.