Triple
T26980319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brihadeeswara |
E679583
|
entity |
| Predicate | associatedTempleDynasty |
P200571
|
FINISHED |
| Object | Chola dynasty |
—
|
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: Chola dynasty | Statement: [Brihadeeswara, associatedTempleDynasty, Chola dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTempleDynasty Context triple: [Brihadeeswara, associatedTempleDynasty, Chola dynasty]
-
A.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
B.
associatedWithTempleComplex
Indicates a relationship in which an entity is connected or related to a specific temple complex, such as by location, function, use, or historical association.
-
C.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
D.
associatedWithDynastyFoundation
Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
-
E.
linkedTempleDeity
Indicates a relationship where a temple is associated with, or dedicated to, a particular deity.
- F. None of above. chosen
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_69eeeb507a7081909d516e1fa08b7d29 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
| PDg | Predicate description generation | batch_69ff976281888190a2e872296fb4a661 |
completed | May 9, 2026, 8:21 p.m. |
Created at: April 27, 2026, 6:45 a.m.