Triple
T23371996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Матуа |
E593498
|
entity |
| Predicate | имеетЮрисдикцию |
P808
|
FINISHED |
| Object | Российская Федерация |
—
|
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: Российская Федерация | Statement: [Матуа, имеетЮрисдикцию, Российская Федерация]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: имеетЮрисдикцию Context triple: [Матуа, имеетЮрисдикцию, Российская Федерация]
-
A.
definedJurisdictionOf
Indicates that one entity formally establishes or specifies the scope, boundaries, or authority of another entity’s jurisdiction.
-
B.
hasJurisdictionOver
chosen
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
C.
mayHaveJurisdictionOver
Indicates that one authority, entity, or body is potentially empowered to exercise legal or official control over another entity, case, or matter.
-
D.
territorialJurisdictionIncludes
Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
-
E.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.