Triple
T19966927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of Kakheti |
E479959
|
entity |
| Predicate | hasMonarchicForm |
P21959
|
FINISHED |
| Object | feudal monarchy |
—
|
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: feudal monarchy | Statement: [King of Kakheti, hasMonarchicForm, feudal monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonarchicForm Context triple: [King of Kakheti, hasMonarchicForm, feudal monarchy]
-
A.
isMonarchicalStyle
Indicates that the relationship or action involves having or using a monarchical style, such as a royal or sovereign form of address or title.
-
B.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
C.
monarchType
chosen
Indicates the specific kind or category of monarchy or monarch associated with an entity.
-
D.
hasCentralizedMonarchy
Indicates that a political entity is governed by a single monarch who holds primary, centralized authority over the state.
-
E.
monarchy
Indicates a system of governance in which supreme authority is vested in a single ruler, typically a king or queen, whose position is usually hereditary.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc5e41881908c1e8867820f1c0c |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.