Triple
T2719456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shauraseni Prakrit |
E60046
|
entity |
| Predicate | approximateEra |
P877
|
FINISHED |
| Object | 1st millennium CE |
—
|
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: 1st millennium CE | Statement: [Shauraseni Prakrit, approximateEra, 1st millennium CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateEra Context triple: [Shauraseni Prakrit, approximateEra, 1st millennium CE]
-
A.
representsEra
Indicates that one entity designates the historical era, period, or age to which another entity belongs or is associated.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
positionInEra
Indicates the temporal placement or role of something within a specific historical or chronological era.
-
D.
approximateStartCenturyBC
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
-
E.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaaee104819085966bc54d5da9c0 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.