Triple
T26508667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emperor of Vijayanagara |
E669619
|
entity |
| Predicate | hadVassals |
P7255
|
FINISHED |
| Object | Nayaka chieftains |
—
|
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: Nayaka chieftains | Statement: [Emperor of Vijayanagara, hadVassals, Nayaka chieftains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadVassals Context triple: [Emperor of Vijayanagara, hadVassals, Nayaka chieftains]
-
A.
vassalsOf
chosen
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
B.
vassalageOver
Indicates a hierarchical feudal relationship in which one party is a vassal subordinate to and owing allegiance or obligations to another.
-
C.
grantedFiefOf
Indicates that one party has been formally given control or ownership of a fief (landed estate) by another authority.
-
D.
hadPrincipality
Indicates that an entity possessed or governed a principality as its domain or territory.
-
E.
vassalageStart
Indicates the point in time when a vassalage relationship—where one party becomes subordinate or owes allegiance to another—officially 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6138fa6e881908d60d7d354ee2b4e |
completed | May 2, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:18 a.m.