Triple
T29717712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Peremyshl |
E751960
|
entity |
| Predicate | typeOfTerritorialRule |
P21438
|
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: [Prince of Peremyshl, typeOfTerritorialRule, appanage principality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTerritorialRule Context triple: [Prince of Peremyshl, typeOfTerritorialRule, appanage principality]
-
A.
typeOfTerritorialDesignation
Indicates the specific category or kind of territorial designation that applies to a given area or jurisdiction.
-
B.
territoryType
chosen
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
C.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
D.
coRuledTerritoryWith
Indicates that two or more rulers shared authority over the same territory during an overlapping period of rule.
-
E.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 28, 2026, 7:35 p.m.