Triple
T28588622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaravati |
E723578
|
entity |
| Predicate | laterPatronage |
P54097
|
FINISHED |
| Object | Ikshvaku 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: Ikshvaku dynasty | Statement: [Amaravati, laterPatronage, Ikshvaku dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPatronage Context triple: [Amaravati, laterPatronage, Ikshvaku dynasty]
-
A.
laterPatron
chosen
Indicates that one entity serves as a patron of another at a later time than some reference patronage relationship.
-
B.
patronage
Indicates a relationship where one party supports, sponsors, or protects another, often in exchange for loyalty, services, or influence.
-
C.
patronageFrom
Indicates a relationship where support, sponsorship, or backing is provided to someone or something by a patron.
-
D.
historicalPatron
Indicates that one entity served as a patron or sponsor of another in a historical context, providing support, protection, or resources.
-
E.
inceptionOfPatronage
Indicates the point in time or event at which a patronage relationship between parties begins.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 28, 2026, 4:19 a.m.