Triple
T31550588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hemshin |
E804988
|
entity |
| Predicate | primaryRegionOfResidence |
P75000
|
FINISHED |
| Object | northeastern Black Sea region of Turkey |
—
|
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: northeastern Black Sea region of Turkey | Statement: [Hemshin, primaryRegionOfResidence, northeastern Black Sea region of Turkey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRegionOfResidence Context triple: [Hemshin, primaryRegionOfResidence, northeastern Black Sea region of Turkey]
-
A.
traditionalRegionOfResidence
Indicates the customary or historically established geographic region where an entity (typically a person or group) resides or is considered to be from.
-
B.
regionOfHabitation
chosen
Indicates the geographic area or environment in which an entity typically lives or resides.
-
C.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
-
D.
primaryLocationIn
Indicates that an entity’s main or most significant location is within or at the referenced place.
-
E.
homeCityRegion
Indicates the city or broader regional area that serves as an entity’s primary place of residence or origin.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 10:10 p.m.