Triple
T25231648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harihara I |
E632232
|
entity |
| Predicate | wasFirstRulerOf |
P3535
|
FINISHED |
| Object | Vijayanagara Empire |
—
|
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: Vijayanagara Empire | Statement: [Harihara I, wasFirstRulerOf, Vijayanagara Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstRulerOf Context triple: [Harihara I, wasFirstRulerOf, Vijayanagara Empire]
-
A.
firstMonarch
chosen
Indicates that the subject is the first monarch (initial ruler) of the object polity or domain.
-
B.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
C.
predecessorAsSupremeRuler
Indicates that one entity previously held the position of supreme ruler immediately before another entity.
-
D.
wasEmperorOf
Indicates that one entity held the position and authority of emperor over another entity (typically a state, empire, or territory).
-
E.
traditionalFirstEmperor
Indicates that the subject is regarded, in traditional or legendary accounts, as the first emperor of the object polity or realm.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cc8b158819095e054bcde25648f |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:06 p.m.