Triple
T36217165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naravarman |
E1047729
|
entity |
| Predicate | notableInscriptions |
P156954
|
FINISHED |
| Object | Dhara inscriptions |
E460676
|
NE 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: Dhara inscriptions | Statement: [Naravarman, notableInscriptions, Dhara inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableInscriptions Context triple: [Naravarman, notableInscriptions, Dhara inscriptions]
-
A.
notableInscriptionBy
Indicates that an inscription of particular note or significance on an entity was created, authored, or carved by a specified agent.
-
B.
attestedInInscriptions
chosen
Indicates that evidence for the entity is documented or recorded in one or more inscriptions.
-
C.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
D.
commonlyInscribedIn
Indicates that something is typically written, carved, or engraved onto a particular surface, object, or medium.
-
E.
oftenDepictedWithInscription
Indicates that the subject is frequently shown or represented together with a written inscription.
- F. None of above.
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_69f76e42c878819095c8d19c0267fb87 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3934297a34819092323eb7670e031f |
completed | June 22, 2026, 1:10 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.