Triple
T26913355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huliaipole region |
E677449
|
entity |
| Predicate | typeOfHistoricalSpace |
P46970
|
FINISHED |
| Object | rural insurgent zone |
—
|
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: rural insurgent zone | Statement: [Huliaipole region, typeOfHistoricalSpace, rural insurgent zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHistoricalSpace Context triple: [Huliaipole region, typeOfHistoricalSpace, rural insurgent zone]
-
A.
historicalType
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
B.
historicLocationType
chosen
Indicates the specific kind or category of a place based on its historical significance or role.
-
C.
historicalStructure
Indicates that the subject is a structure recognized for its historical significance or heritage value.
-
D.
historicalSettlementType
Indicates the type or category of settlement an entity was historically classified as (e.g., village, town, city) during a past period.
-
E.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
- 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_69eee9bcef1c8190be88586bb902bb9b |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: April 27, 2026, 6:03 a.m.