Triple
T18884658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramanuja Jayanti |
E461927
|
entity |
| Predicate | correspondsToGregorianMonths |
P16936
|
FINISHED |
| Object | March |
—
|
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: March | Statement: [Ramanuja Jayanti, correspondsToGregorianMonths, March]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correspondsToGregorianMonths Context triple: [Ramanuja Jayanti, correspondsToGregorianMonths, March]
-
A.
correspondsRoughlyToGregorianMonths
chosen
Indicates that one or more time periods or units align approximately, but not exactly, with specific months in the Gregorian calendar.
-
B.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
-
C.
calendarYearOffsetFromGregorian
Indicates the number of whole calendar years by which a given calendar system is offset relative to the Gregorian calendar.
-
D.
relationshipToGregorianCalendar
Indicates how a given calendar date or system corresponds or relates to the Gregorian calendar.
-
E.
dateRelativeToGregorian
Indicates how a given date is positioned or expressed in relation to the standard Gregorian calendar date.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d53e608190b8740c092b6e1523 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:57 a.m.