Triple
T20150696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindu solar calendar |
E491425
|
entity |
| Predicate | definesMonthBy |
P138864
|
FINISHED |
| Object | Sun’s transit through a zodiac sign |
—
|
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: Sun’s transit through a zodiac sign | Statement: [Hindu solar calendar, definesMonthBy, Sun’s transit through a zodiac sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMonthBy Context triple: [Hindu solar calendar, definesMonthBy, Sun’s transit through a zodiac sign]
-
A.
monthObserved
Indicates the month during which an event, observation, or measurement took place.
-
B.
proposedInMonth
Indicates that an entity (such as a proposal or plan) was formally proposed during a specific calendar month.
-
C.
hasMonth
Indicates that something is associated with, occurs in, or is assigned to a specific month.
-
D.
monthName
Indicates that one entity is the name (in words) of the month represented by the other entity.
-
E.
monthName2
Indicates that two entities are associated as the same calendar month, where one provides the month’s name and the other represents that month in another form (such as a number or date).
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667a1c5848190975b17ab07251f8b |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:33 p.m.