Triple
T23302240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jethwa Rajput chiefdoms |
E590333
|
entity |
| Predicate | notableSuccessorState |
P71924
|
FINISHED |
| Object | Porbandar princely 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: Porbandar princely state | Statement: [Jethwa Rajput chiefdoms, notableSuccessorState, Porbandar princely state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSuccessorState Context triple: [Jethwa Rajput chiefdoms, notableSuccessorState, Porbandar princely state]
-
A.
notableSuccessor
chosen
Indicates that one entity is a prominent or historically significant successor to another in a sequence or lineage.
-
B.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
C.
successorStateFlag
Indicates that a particular state directly follows another state in a defined sequence or process.
-
D.
notableSuccessorUnit
Indicates that one unit is recognized as a particularly significant or prominent successor to another unit in a sequence or lineage.
-
E.
successorStateRepresentedLater
Indicates that one state is a later representation or subsequent version of another state in a temporal or sequential progression.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972406a08190bbf355cc7a9f8432 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.