Triple
T25293936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nayaka period |
E634164
|
entity |
| Predicate | hasRulingElite |
P134711
|
FINISHED |
| Object | Nayaka rulers |
—
|
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: Nayaka rulers | Statement: [Nayaka period, hasRulingElite, Nayaka rulers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulingElite Context triple: [Nayaka period, hasRulingElite, Nayaka rulers]
-
A.
isEliteUnit
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
B.
hasTypeOfRuler
Indicates that one entity serves as the specific kind or category of ruler (e.g., monarch, dictator, president) that characterizes or governs another entity.
-
C.
hasNoble
Indicates that one entity possesses or is associated with a noble title, status, or noble individual.
-
D.
hasSignificantRuler
chosen
Indicates that an entity has or had a ruler whose leadership is considered historically or contextually important.
-
E.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd007388190a7d80ea457119072 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.