Triple
T7302320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nawab of Bihar |
E167886
|
entity |
| Predicate | hasRulershipType |
P27868
|
FINISHED |
| Object | regional rulership |
—
|
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: regional rulership | Statement: [Nawab of Bihar, hasRulershipType, regional rulership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulershipType Context triple: [Nawab of Bihar, hasRulershipType, regional rulership]
-
A.
hasTypeOfRuler
chosen
Indicates that one entity serves as the specific kind or category of ruler (e.g., monarch, dictator, president) that characterizes or governs another entity.
-
B.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
C.
hasNumberOfRulers
Indicates the quantity of rulers associated with or governing a given entity.
-
D.
hasFamousRuler
Indicates that an entity is or was ruled by a ruler who is widely recognized or historically notable.
-
E.
hasViewOfKingdom
Indicates that an entity has a vantage point from which it can see or overlook a kingdom.
- 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb09164819099c4479d48c1688a |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.