Triple
T21625464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wankaner |
E533688
|
entity |
| Predicate | princelyStateClass |
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: [Wankaner, princelyStateClass, salute state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: princelyStateClass Context triple: [Wankaner, princelyStateClass, salute state]
-
A.
princelyStateCategory
chosen
Indicates that an entity is classified as belonging to the category of princely states.
-
B.
princelyStateName
Indicates that an entity has the name of a princely state (a semi-autonomous, traditionally monarch-ruled territory).
-
C.
notablePrincelyState
Indicates that an entity is recognized as a historically significant princely state, typically within a larger imperial or colonial framework.
-
D.
containsFormerPrincelyState
Indicates that a geopolitical entity includes within its boundaries an area that was once a princely state.
-
E.
ruledPrincipality
Indicates that one entity exercised governing authority over a principality as its ruler.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef52121c3c8190b9b4d862ed247c71 |
completed | April 27, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.