Triple
T37704991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudradaman I |
E939174
|
entity |
| Predicate | inscriptionSite |
P23382
|
FINISHED |
| Object | Junagadh (Girnar) rock |
—
|
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: Junagadh (Girnar) rock | Statement: [Rudradaman I, inscriptionSite, Junagadh (Girnar) rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionSite Context triple: [Rudradaman I, inscriptionSite, Junagadh (Girnar) rock]
-
A.
inscriptionFormula
Indicates that one entity bears or contains a specific inscribed text, phrase, or formula associated with it.
-
B.
inscriptionSupport
Indicates that one entity serves as the physical surface or material on which another entity (an inscription) is written, carved, or otherwise recorded.
-
C.
inscriptionForm
Indicates the physical or structural form in which an inscription is presented (e.g., carved, painted, stamped, or otherwise rendered).
-
D.
inscription
Indicates that text has been written, carved, or engraved onto a surface or object.
-
E.
inscriptionLocation
chosen
Indicates the place or surface on which an inscription is written or engraved.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.