Triple
T28588640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaravati |
E723578
|
entity |
| Predicate | languageHistoricalInscriptions |
P156954
|
FINISHED |
| Object | Prakrit |
—
|
NE NERFINISHED |
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: Prakrit | Statement: [Amaravati, languageHistoricalInscriptions, Prakrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageHistoricalInscriptions Context triple: [Amaravati, languageHistoricalInscriptions, Prakrit]
-
A.
pyramidTextInscriptions
Indicates that the subject has text inscriptions located on or within a pyramid.
-
B.
attestedInInscriptions
chosen
Indicates that evidence for the entity is documented or recorded in one or more inscriptions.
-
C.
officialLanguageOfInscriptions
Indicates the language officially used in the inscriptions associated with a particular entity.
-
D.
secondaryLanguageOfInscriptions
Indicates that a specified language serves as the secondary language used in the inscriptions associated with a given entity.
-
E.
inscriptionsLanguage
Indicates that the language used in the inscriptions on an object or surface is the specified language.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 28, 2026, 4:19 a.m.