Triple
T28402026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veshenskaya |
E719416
|
entity |
| Predicate | isCossackSettlement |
P164464
|
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: [Veshenskaya, isCossackSettlement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCossackSettlement Context triple: [Veshenskaya, isCossackSettlement, true]
-
A.
isIndigenousSettlementType
Indicates that the settlement type is one that is traditionally established, inhabited, or defined by an Indigenous people or community.
-
B.
isRuralSettlement
Indicates that a settlement is located in a rural area, typically characterized by low population density and limited urban infrastructure.
-
C.
isOneOfOlderSettlementsIn
Indicates that an entity is among the earlier or historically older settlements located within a specified area or region.
-
D.
isLocatedInSettlement
Indicates that an entity is situated within or belongs to a specific human settlement, such as a town, village, or city.
-
E.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
- F. None of above. chosen
Provenance (4 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d6d0b908190a272f7e51d6be67c |
completed | May 2, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f64bca8574819095e081cbb7e2f369 |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 28, 2026, 1:20 a.m.