Triple
T26601837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pala dynasty |
E667655
|
entity |
| Predicate | patronizedInstitution |
P161591
|
FINISHED |
| Object | Somapura Mahavihara |
E671091
|
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: Somapura Mahavihara | Statement: [Pala dynasty, patronizedInstitution, Somapura Mahavihara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronizedInstitution Context triple: [Pala dynasty, patronizedInstitution, Somapura Mahavihara]
-
A.
patronizedInstitution
chosen
Indicates that one entity regularly used, supported, or was a customer of a particular institution.
-
B.
sponsoringInstitution
Indicates that an institution provides financial or organizational support to enable or underwrite an activity, project, event, or entity.
-
C.
promotedByInstitution
Indicates that an institution advances, supports, or publicizes something, contributing to its recognition, adoption, or success.
-
D.
establishedInstitution
Indicates that an entity founded, created, or formally set up an institution or organization.
-
E.
centralInstitutionOf
Indicates that one institution serves as the primary or main institutional center for another entity, such as an organization, system, or region.
- 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_69ee9cfd20348190bb1255d2603efb7a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11c8415e048190a6e94d953734c0eb |
completed | May 23, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 2:12 a.m.