Triple
T4531302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasdan State |
E106302
|
entity |
| Predicate | typeOfPrincelyState |
P45258
|
FINISHED |
| Object | salute state |
—
|
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: salute state | Statement: [Jasdan State, typeOfPrincelyState, salute state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPrincelyState Context triple: [Jasdan State, typeOfPrincelyState, salute state]
-
A.
princelyStateCategory
chosen
Indicates that an entity is classified as belonging to the category of princely states.
-
B.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
C.
monarchType
Indicates the specific kind or category of monarchy or monarch associated with an entity.
-
D.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
E.
endedAsPrincipality
Indicates that an entity’s existence or historical development concluded with it having the political status of a principality.
- 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579d7a88819083eb0620ca176f2e |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:03 p.m.