Triple
T20631749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artyomovsk |
E506971
|
entity |
| Predicate | hasMapLabelStatus |
P12717
|
FINISHED |
| Object | largely replaced by Bakhmut on modern Ukrainian maps |
—
|
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: largely replaced by Bakhmut on modern Ukrainian maps | Statement: [Artyomovsk, hasMapLabelStatus, largely replaced by Bakhmut on modern Ukrainian maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMapLabelStatus Context triple: [Artyomovsk, hasMapLabelStatus, largely replaced by Bakhmut on modern Ukrainian maps]
-
A.
hasLabel
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
B.
hasMaps
Indicates that one entity possesses, includes, or provides access to one or more maps associated with another entity.
-
C.
hasStatusLabel
chosen
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
D.
hasLabelSet
Indicates that an entity is associated with a specific collection or set of labels.
-
E.
hasMapRegion
Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
- 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_69e0b4bd4a0081908d4e97a590a33fb2 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6ad0b0508819093c62a4ceaf860ce |
completed | April 20, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69e5a0155bd48190b3c769a12cc2c83d |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 16, 2026, 11:42 a.m.