Triple
T18887023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaravati Stupa |
E461982
|
entity |
| Predicate | developedUntil |
P80498
|
FINISHED |
| Object | circa 3rd 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: circa 3rd century CE | Statement: [Amaravati Stupa, developedUntil, circa 3rd century CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedUntil Context triple: [Amaravati Stupa, developedUntil, circa 3rd century CE]
-
A.
developedAt
Indicates the place or location where something was created, built, or developed.
-
B.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
C.
developsUntil
chosen
Indicates that a process, condition, or entity continues to develop or progress up to a specified point or limit in time or state.
-
D.
developedThrough
Indicates that something came into existence, was created, or was brought to its current form by means of a specified process, method, or developmental pathway.
-
E.
developmentDate
Indicates the date on which something was created, developed, or brought into existence.
- 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_69e5c4777434819098850da0ee1c6b43 |
completed | April 20, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e27e1481908a8da10b28f07875 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.