Triple
T22073788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pala period |
E545473
|
entity |
| Predicate | hasNotableSubjectMatter |
P494
|
FINISHED |
| Object | Buddha images |
—
|
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: Buddha images | Statement: [Pala period, hasNotableSubjectMatter, Buddha images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSubjectMatter Context triple: [Pala period, hasNotableSubjectMatter, Buddha images]
-
A.
hasNotableSubject
chosen
Indicates that an entity is associated with a subject that is particularly significant, prominent, or noteworthy in relation to it.
-
B.
hasLegalSubject
Indicates that an entity serves as the legal subject (e.g., rights-holder or obligated party) in a legal relationship or context.
-
C.
hasNotableClaim
Indicates that an entity is associated with a significant, widely recognized statement, assertion, or claim.
-
D.
hasNotableIssue
Indicates that an entity is associated with a significant problem, concern, or defect that is noteworthy or exceptional compared to typical cases.
-
E.
hasNotableWord
Indicates that an entity is associated with a word or term that is considered notable, distinctive, or significant in some context.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288affb081908b64742f7bf467fa |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:28 p.m.