Triple
T33097490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lysychansk |
E846949
|
entity |
| Predicate | administrativeStatusBefore2022 |
P94446
|
FINISHED |
| Object | city of oblast significance in Luhansk Oblast |
—
|
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: city of oblast significance in Luhansk Oblast | Statement: [Lysychansk, administrativeStatusBefore2022, city of oblast significance in Luhansk Oblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: administrativeStatusBefore2022 Context triple: [Lysychansk, administrativeStatusBefore2022, city of oblast significance in Luhansk Oblast]
-
A.
statusBefore2022
chosen
Indicates that an entity’s status or condition is defined as it existed prior to the year 2022.
-
B.
administrativeStatusBefore1986
Indicates the administrative status or classification that an entity held prior to the year 1986.
-
C.
formerAdministrativeStatus
Indicates that an entity previously held, but no longer holds, a particular administrative status or role.
-
D.
hasAdministrativeStatusSince
Indicates that an entity has held a particular administrative status continuously from a specified point in time onward.
-
E.
statusBefore2016
Indicates the status or condition that an entity had prior to the year 2016.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 1, 2026, 1:26 a.m.