Triple
T37950875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rana Udai Singh II |
E946739
|
entity |
| Predicate | successorDispute |
P32191
|
FINISHED |
| Object | Jagmal Singh |
—
|
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: Jagmal Singh | Statement: [Rana Udai Singh II, successorDispute, Jagmal Singh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDispute Context triple: [Rana Udai Singh II, successorDispute, Jagmal Singh]
-
A.
successorDisputesInvolved
Indicates involvement in disputes or conflicts arising from succession or succession-related claims.
-
B.
settledSuccessionDisputeBetween
Indicates that an entity resolved or brought to an end a conflict over inheritance or succession between two or more parties.
-
C.
successionIssue
Indicates a relationship where there is a dispute, complication, or question regarding who is entitled to succeed or inherit a position, title, or estate.
-
D.
successionConflict
chosen
Indicates a dispute or struggle over who has the legitimate right to succeed to a position, title, or authority.
-
E.
legalSuccessorClaim
Indicates that one entity asserts it is the lawful successor or inheritor of another entity’s rights, status, or authority.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:20 p.m.