Triple
T4114949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anjukladang inscription |
E90268
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Javanese inscription |
C14751
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: ancient Javanese inscription Context triple: [Anjukladang inscription, instanceOf, ancient Javanese inscription]
-
A.
Srivijaya inscription
A Srivijaya inscription is an ancient written record, typically in Old Malay or Sanskrit, produced by the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
B.
Srivijayan inscription
A Srivijayan inscription is an ancient written record, typically carved in stone or metal, produced under the Srivijaya maritime empire to document royal decrees, religious dedications, political events, or administrative matters.
-
C.
7th-century inscription
A 7th-century inscription is a text carved, engraved, or written on a durable material during the 600s CE, providing contemporary evidence of the language, culture, and historical events of that period.
-
D.
Achaemenid inscription
An Achaemenid inscription is a formal text carved or written on durable materials during the Achaemenid Empire, typically in multiple languages and scripts, to record royal proclamations, commemorations, or religious dedications.
-
E.
inscribed stone slab
An inscribed stone slab is a flat piece of stone bearing carved or engraved text, symbols, or images, typically used for commemorative, religious, legal, or informational purposes.
- F. None of above. chosen
Provenance (1 batch)
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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:41 p.m.