Triple
T34459242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaduraya Wodeyar |
E884586
|
entity |
| Predicate | successorDynastyRuled |
P1551
|
FINISHED |
| Object | Kingdom of Mysore |
—
|
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: Kingdom of Mysore | Statement: [Yaduraya Wodeyar, successorDynastyRuled, Kingdom of Mysore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorDynastyRuled Context triple: [Yaduraya Wodeyar, successorDynastyRuled, Kingdom of Mysore]
-
A.
successorDynastyFoundedBy
Indicates that the successor dynasty was established or founded by the referenced person or group.
-
B.
successorDynastyBecame
Indicates that one dynasty replaced another and formally became its successor.
-
C.
successorDynasty
chosen
Indicates that one dynasty directly follows and replaces another in a sequence of rule or authority.
-
D.
successorDynastyOrigin
Indicates the place or cultural-geographic origin from which a successor dynasty arises in relation to its predecessor.
-
E.
successorDynastyDeFacto
Indicates that one dynasty effectively functioned as the successor to another in practice, regardless of formal or legally recognized succession.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
Created at: May 1, 2026, 2 a.m.