Triple
T10576998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kshatriya |
E249634
|
entity |
| Predicate | femaleDesignation |
P72639
|
FINISHED |
| Object | Kshatriyani |
—
|
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: Kshatriyani | Statement: [Kshatriya, femaleDesignation, Kshatriyani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: femaleDesignation Context triple: [Kshatriya, femaleDesignation, Kshatriyani]
-
A.
femaleAbbreviation
Indicates that one entity is an abbreviation or shortened form specifically denoting a female version of another entity.
-
B.
femaleHas
Indicates that a specified entity is female or possesses a female gender attribute in relation to another entity or context.
-
C.
femaleFeature
Indicates that the subject possesses a characteristic or attribute that is typically associated with females.
-
D.
femaleBranch
Indicates that one entity is a female branch or female-line subdivision of another entity within a hierarchical or genealogical structure.
-
E.
femaleAddressedAs
chosen
Indicates that a female individual is referred to or addressed by a particular name, title, or form of address.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5275628988190bd00dd3f8d7c3937 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:38 p.m.