Triple
T33607473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohilla Afghan |
E860898
|
entity |
| Predicate | laterPrincelyState |
P201423
|
FINISHED |
| Object | Rampur State |
—
|
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: Rampur State | Statement: [Rohilla Afghan, laterPrincelyState, Rampur State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPrincelyState Context triple: [Rohilla Afghan, laterPrincelyState, Rampur State]
-
A.
princelyStateCategory
Indicates that an entity is classified as belonging to the category of princely states.
-
B.
notablePrincelyState
Indicates that an entity is recognized as a historically significant princely state, typically within a larger imperial or colonial framework.
-
C.
princelyStateName
Indicates that an entity has the name of a princely state (a semi-autonomous, traditionally monarch-ruled territory).
-
D.
containsFormerPrincelyState
Indicates that a geopolitical entity includes within its boundaries an area that was once a princely state.
-
E.
wasPrincelyStateUntil
Indicates that an entity held the status of a princely state up to a specified end date or time period.
- F. None of above. chosen
Provenance (4 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
| PDg | Predicate description generation | batch_69fff4525ce48190b1d760539e68aadc |
completed | May 10, 2026, 2:58 a.m. |
Created at: May 1, 2026, 1:41 a.m.