Triple
T8198131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexinsky Uyezd |
E191485
|
entity |
| Predicate | usedInAdministrativeSystem |
P66166
|
FINISHED |
| Object | Russian Empire guberniya–uyezd system |
—
|
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: Russian Empire guberniya–uyezd system | Statement: [Alexinsky Uyezd, usedInAdministrativeSystem, Russian Empire guberniya–uyezd system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAdministrativeSystem Context triple: [Alexinsky Uyezd, usedInAdministrativeSystem, Russian Empire guberniya–uyezd system]
-
A.
usedAdministrativeSystemOf
Indicates that one entity made use of another entity’s administrative system to perform or manage its administrative functions.
-
B.
operatesInAdministrativeSystem
chosen
Indicates that an entity functions or carries out its activities within a specified administrative or bureaucratic system.
-
C.
usedForAdministrativePurposes
Indicates that something is employed in managing, organizing, or overseeing official, institutional, or organizational activities and records.
-
D.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
E.
administeredIn
Indicates that an action, treatment, or process is carried out or applied within a specific location, context, or 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_69ca82c6e9548190a4c5ca14516e4417 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c2341f881908be59c378896e5bc |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.