Triple
T27221696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simeon Ivanovich of Kaluga |
E681292
|
entity |
| Predicate | typeOfPrincipality |
P45258
|
FINISHED |
| Object | appanage principality |
—
|
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: appanage principality | Statement: [Simeon Ivanovich of Kaluga, typeOfPrincipality, appanage principality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPrincipality Context triple: [Simeon Ivanovich of Kaluga, typeOfPrincipality, appanage principality]
-
A.
ruledPrincipality
Indicates that one entity exercised governing authority over a principality as its ruler.
-
B.
wasEcclesiasticalPrincipality
Indicates that an entity functioned as a territorial state or principality governed by ecclesiastical (religious) authorities rather than secular rulers.
-
C.
princelyStateCategory
chosen
Indicates that an entity is classified as belonging to the category of princely states.
-
D.
lordshipType
Indicates the specific kind or category of lordship relationship that exists between one entity and another.
-
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_69eefac9f64c8190a07490fe0c8b72a3 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 27, 2026, 9:43 a.m.