Triple
T19254036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nawab of Bhopal |
E481467
|
entity |
| Predicate | hasGenderTradition |
P20413
|
FINISHED |
| Object | male rulers |
—
|
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: male rulers | Statement: [Nawab of Bhopal, hasGenderTradition, male rulers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenderTradition Context triple: [Nawab of Bhopal, hasGenderTradition, male rulers]
-
A.
hasGenderInSomeTraditions
chosen
Indicates that, in at least some cultural, religious, or historical traditions, the subject is regarded as having a specific gender.
-
B.
hasGenderConvention
Indicates that there is an established or customary way of assigning or expressing gender within a given context, system, or culture.
-
C.
hasGenderDivisions
Indicates that something is organized, classified, or separated into groups based on gender.
-
D.
hasGenderSystem
Indicates that an entity employs or is characterized by a particular system for categorizing gender.
-
E.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb3339648190a87d38ce42aff016 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:28 p.m.