Triple
T32137689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sloviansk |
E820815
|
entity |
| Predicate | isPartOfFrontlineRegion |
P53598
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sloviansk, isPartOfFrontlineRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfFrontlineRegion Context triple: [Sloviansk, isPartOfFrontlineRegion, true]
-
A.
frontLineRegion
chosen
Indicates that a region is located at or constitutes the primary area of direct engagement or contact in a conflict, competition, or critical situation.
-
B.
isFrontlineUnit
Indicates that an entity functions as a primary combat or operational unit positioned at or near the front line of engagement.
-
C.
wasFrontlineAreaDuring
Indicates that a location served as a primary combat or conflict zone during a specified time period.
-
D.
wasFrontierRegion
Indicates that a region historically functioned as a frontier area, marking a boundary or border zone between larger political or cultural entities.
-
E.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 1, 2026, 12:30 a.m.