Triple
T32851391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleshky Sich |
E840260
|
entity |
| Predicate | regionHistoricallyIn |
P63734
|
FINISHED |
| Object | Southern Ruthenia |
—
|
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: Southern Ruthenia | Statement: [Oleshky Sich, regionHistoricallyIn, Southern Ruthenia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionHistoricallyIn Context triple: [Oleshky Sich, regionHistoricallyIn, Southern Ruthenia]
-
A.
regionHistory
chosen
Indicates that there exists a historical or past association between a subject and a specific geographic or administrative region.
-
B.
historicallyBasedIn
Indicates that one entity is located in or associated with a place as its base of operations during a specific historical period.
-
C.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
D.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
E.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
- 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_69f349412c78819084459850e11d29f7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:17 a.m.