Triple
T26536523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijayanagara Empire royal family |
E671264
|
entity |
| Predicate | secondaryEthnicBase |
P78143
|
FINISHED |
| Object | Telugu |
—
|
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: Telugu | Statement: [Vijayanagara Empire royal family, secondaryEthnicBase, Telugu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryEthnicBase Context triple: [Vijayanagara Empire royal family, secondaryEthnicBase, Telugu]
-
A.
laterEthnicIdentity
Indicates that an entity’s ethnic identity is associated with or applies to a later period in time relative to some earlier state or context.
-
B.
primaryEthnicFocus
Indicates that something is chiefly oriented toward, concerned with, or designed for a particular ethnic group as its main focus.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
secondaryAncestry
chosen
Indicates a secondary or additional ancestral relationship that an entity has beyond its primary ancestry.
-
E.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
- 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_69eeb3206e748190b90c85cc81f38c91 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 1:39 a.m.