Triple
T35684890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BM |
E1031114
|
entity |
| Predicate | assignedToAdministrativeUnit |
P3892
|
FINISHED |
| Object | Sumy Oblast |
—
|
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: Sumy Oblast | Statement: [BM, assignedToAdministrativeUnit, Sumy Oblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignedToAdministrativeUnit Context triple: [BM, assignedToAdministrativeUnit, Sumy Oblast]
-
A.
laterAdministrativeUnit
Indicates that one administrative unit succeeds or replaces another in time, coming into effect at a later date.
-
B.
hasAdministrativeUnit
chosen
Indicates that one entity possesses, contains, or is associated with another entity that functions as its administrative subdivision or governing unit.
-
C.
successorAdministrativeUnit
Indicates that one administrative unit has officially replaced another in its governing or jurisdictional role.
-
D.
connectsAdministrativeUnits
Indicates a relationship where one administrative unit is linked or associated with another for governance, coordination, or organizational purposes.
-
E.
representsAdministrativeUnit
Indicates that one entity serves as or corresponds to the administrative unit governing or organizing 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.