Triple
T23240180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kankali Tila |
E581417
|
entity |
| Predicate | yieldsTypeOfArtifact |
P40733
|
FINISHED |
| Object | Jain votive tablets |
—
|
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: Jain votive tablets | Statement: [Kankali Tila, yieldsTypeOfArtifact, Jain votive tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yieldsTypeOfArtifact Context triple: [Kankali Tila, yieldsTypeOfArtifact, Jain votive tablets]
-
A.
hasTypeOfArtifact
chosen
Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
-
B.
artifactType
Indicates the specific kind or category of artifact that an entity is classified as.
-
C.
testArtifact
Indicates that an entity serves as an artifact or item used for testing, validation, or experimentation in a process or system.
-
D.
relatedArtifactType
Indicates the specific kind of relationship or linkage that one artifact has to another artifact (e.g., predecessor, successor, reference, dependency).
-
E.
artworkType
Indicates the specific category or kind of artwork that characterizes the relationship between the subject and the artwork.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192ecc7e481908cac59df5c0deea1 |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.