Triple
T6621130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vistula Land |
E149674
|
entity |
| Predicate | policeControl |
P71567
|
FINISHED |
| Object | Russian imperial authorities |
—
|
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 imperial authorities | Statement: [Vistula Land, policeControl, Russian imperial authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeControl Context triple: [Vistula Land, policeControl, Russian imperial authorities]
-
A.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
B.
townControlled
Indicates that one entity has governing authority or administrative control over a town.
-
C.
lawEnforcementResponse
Indicates the actions or measures taken by law enforcement agencies in reaction to an incident, behavior, or situation.
-
D.
policeBureau
Indicates that an entity functions as or is associated with a police bureau or police department.
-
E.
policeUnit
Indicates that one entity is a police unit (such as a department, squad, or division) associated with or responsible for another entity.
- F. None of above. chosen
Provenance (4 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6bdb76ec48190b59d576170970cc9 |
completed | March 27, 2026, 5:26 p.m. |
Created at: March 27, 2026, 1:58 p.m.