Triple
T36812767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banavasi region |
E909639
|
entity |
| Predicate | earliestFlourishingCentury |
P127907
|
FINISHED |
| Object | 4th century 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: 4th century CE | Statement: [Banavasi region, earliestFlourishingCentury, 4th century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestFlourishingCentury Context triple: [Banavasi region, earliestFlourishingCentury, 4th century CE]
-
A.
flourishedToCentury
Indicates the century during which an entity reached its peak activity, prominence, or flourishing.
-
B.
approximateFlourishingStartCentury
chosen
Indicates the century in which an entity’s period of flourishing or peak activity is estimated to have begun.
-
C.
flourishedUntilCentury
Indicates the last century during which an entity (such as a person, culture, or institution) was active, prominent, or at its peak before declining or ceasing to flourish.
-
D.
flourishedInCentury
Indicates that an entity experienced its peak activity, influence, or development during a specified century.
-
E.
firstPerformedCentury
Indicates the century in which an action, work, or performance was first carried out or presented.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:13 p.m.