Triple
T32396494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nalanda copper-plate inscription |
E827823
|
entity |
| Predicate | inscriptionCategory |
P174463
|
FINISHED |
| Object | donative inscription |
—
|
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: donative inscription | Statement: [Nalanda copper-plate inscription, inscriptionCategory, donative inscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionCategory Context triple: [Nalanda copper-plate inscription, inscriptionCategory, donative inscription]
-
A.
registrationCategory
Indicates the classification or type under which an entity is formally registered within a system or registry.
-
B.
inscriptionProcess
Indicates the process or method by which an inscription is created, applied, or recorded on a surface or object.
-
C.
inscriptionBy
Indicates that an inscription was created, written, or carved by a particular agent or entity.
-
D.
enrollmentCategory
Indicates the classification or type of enrollment under which an entity is registered or participating.
-
E.
inscriptionLocation
Indicates the place or surface on which an inscription is written or engraved.
- F. None of above. chosen
Provenance (4 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2451e108190a73ccfdc99203d55 |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 12:52 a.m.