Triple
T3317333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yurievichi |
E69711
|
entity |
| Predicate | ruledTerritoryType |
P10006
|
FINISHED |
| Object | 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: principality | Statement: [Yurievichi, ruledTerritoryType, principality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruledTerritoryType Context triple: [Yurievichi, ruledTerritoryType, principality]
-
A.
coRuledTerritoryWith
Indicates that two or more rulers shared authority over the same territory during an overlapping period of rule.
-
B.
governedTerritory
chosen
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
-
C.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
D.
governsTerritoryType
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
E.
ruledFromRegion
Indicates that a ruling authority exercised control or governance over a domain while being based in or operating from a specific region.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb113cb6c8190989b06476f6015fd |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.