Triple
T5200464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhadrapada |
E117379
|
entity |
| Predicate | typicalGregorianSpan |
P18044
|
FINISHED |
| Object | late August to late September |
—
|
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: late August to late September | Statement: [Bhadrapada, typicalGregorianSpan, late August to late September]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGregorianSpan Context triple: [Bhadrapada, typicalGregorianSpan, late August to late September]
-
A.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
B.
followsGregorianCalendar
Indicates that the entity uses or adheres to the Gregorian calendar system for dating and timekeeping.
-
C.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
D.
dateSecularized
Indicates the date on which a religious or ecclesiastical entity was formally converted to secular (non-religious) status.
-
E.
typicalDates
chosen
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
- 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_69bd4463dd3c81909966123f20b79d57 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7adb034c819086bf8a85fbf158f4 |
completed | March 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69bd77b9a67c8190819612257ea746b4 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:47 p.m.