Triple
T32396448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nalanda copper-plate inscription |
E827823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | copper plate inscription |
C48632
|
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: copper plate inscription Context triple: [Nalanda copper-plate inscription, instanceOf, copper plate inscription]
-
A.
copperplate inscription
chosen
A copperplate inscription is a historical document engraved on a copper plate, typically used in ancient and medieval societies to record official grants, decrees, or commemorative texts intended for long-term preservation.
-
B.
Kharoṣṭhī inscription
A Kharoṣṭhī inscription is a written text carved or inscribed using the ancient Kharoṣṭhī script, primarily found on stone, metal, pottery, or other durable materials in the northwestern regions of the Indian subcontinent and Central Asia.
-
C.
ancient inscriptions
Ancient inscriptions are texts or symbols carved, engraved, or written on durable materials such as stone, metal, or clay by past civilizations, serving as primary evidence of their language, culture, beliefs, and historical events.
-
D.
Hebrew inscription
A Hebrew inscription is a text carved, written, or engraved in the Hebrew language and script on a durable surface such as stone, metal, pottery, or parchment, often serving religious, commemorative, legal, or decorative purposes.
-
E.
mosaic inscription
A mosaic inscription is a text or message formed by arranging small, colored pieces of stone, glass, or tile within a mosaic design, typically serving decorative, commemorative, or religious purposes.
- F. None of above.
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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:52 a.m.