Triple
T34751589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokołów Podlaski |
E1001795
|
entity |
| Predicate | partitionPeriodRule |
P43137
|
FINISHED |
| Object | Russian Empire |
—
|
NE NERFINISHED |
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 | Statement: [Sokołów Podlaski, partitionPeriodRule, Russian Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partitionPeriodRule Context triple: [Sokołów Podlaski, partitionPeriodRule, Russian Empire]
-
A.
periodizedAs
chosen
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
layoutPeriod
Indicates the time span or phase during which a particular layout or arrangement is in effect or applied.
-
D.
periodProperty
Indicates a temporal characteristic or attribute associated with a specific time period or interval.
-
E.
capturesPeriod
Indicates that one entity records, encompasses, or represents a specific span of time associated with another entity.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 3:59 p.m.