Triple
T29540205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mahendravarman I |
E749470
|
entity |
| Predicate | issuedInscriptions |
P94398
|
FINISHED |
| Object | Mandagapattu inscription |
—
|
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: Mandagapattu inscription | Statement: [Mahendravarman I, issuedInscriptions, Mandagapattu inscription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuedInscriptions Context triple: [Mahendravarman I, issuedInscriptions, Mandagapattu inscription]
-
A.
issuedInscriptionsIn
Indicates that an entity (such as an authority or issuer) produced or authorized inscriptions within a specified place or context.
-
B.
issuedInscription
chosen
Indicates that an authority or source formally created and released a specific inscription or written record.
-
C.
hasInscriptions
Indicates that an object, surface, or artifact bears written, carved, or engraved inscriptions on it.
-
D.
numberOfInscriptions
Indicates the total count of inscriptions associated with a given entity or object.
-
E.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 5:02 p.m.